Re: Not a v4.0.0 POM error

2009-11-12 Thread Wayne Fay
> $ cat maven-install-plugin-2.3.pom
>  �W[o�6 ~7���  0d�

That's a problem. How did this binary pom file land in your local
cache? Sounds like you've got a misconfiguration somewhere, probably
in your company repo manager/proxy.

Wayne

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



RE: Not a v4.0.0 POM error

2009-11-12 Thread Gerardo Corro

Hi,

Yes, I changed the URL since I need to keep my company privacy, but in any 
case, it's not a public repository, you may need an user and password to get 
the files.

>Who or what put the pom file on the url you are pointing to? Is is some 
>repository manager?

Yes, it's a repo manager.

Thanks!





> Date: Thu, 12 Nov 2009 02:24:31 +0100
> Subject: Re: Not a v4.0.0 POM error
> From: nick.stolw...@gmail.com
> To: users@maven.apache.org
> 
> It is trying to get the remote file and that one (the link you
> provided) does not work on my computer. It may be you have changed the
> link in your mail, or it that it will let you in. But if you get the
> same as me, then there is your problem. Who or what put the pom file
> on the url you are pointing to? Is is some repository manager?
> 
> With regards,
> 
> Nick Stolwijk
> ~Java Developer~
> 
> IPROFS BV.
> Claus Sluterweg 125
> 2012 WS Haarlem
> http://www.iprofs.nl
> 
> 
> 
> On Thu, Nov 12, 2009 at 2:19 AM, Sean Hennessy
>  wrote:
> > Pardon me but usually the .pom is an xml text file.
> > you should be able to open w/ text editor on ubuntu.
> > try using vi or gedit.
> >
> > Sean
> >
> > -Original Message-
> > From: Gerardo Corro [mailto:rob_gar_...@hotmail.com]
> > Sent: Wednesday, November 11, 2009 5:11 PM
> > To: users@maven.apache.org
> > Subject: RE: Not a v4.0.0 POM error
> >
> >
> > It's a valid pom:
> >
> > $ ls -l maven-install-plugin-2.3.pom
> > -rw-r--r-- 1 corro corro 1486 2009-11-12 01:33 maven-install-plugin-2.3.pom 
> > $ file maven-install-plugin-2.3.pom
> > maven-install-plugin-2.3.pom: gzip compressed data, from Unix $ gunzip -c  
> > maven-install-plugin-2.3.pom  
> > http://maven.apache.org/POM/4.0.0";
> > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> > xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> > http://maven.apache.org/xsd/maven-4.0.0.xsd";>
> >  4.0.0
> >
> > and the file continues... however Ubuntu "Archive Manager Tool" can't 
> > extract it, it says the pom has errors.
> >
> > Best regards.
> >
> >
> >> Date: Thu, 12 Nov 2009 01:21:26 +0100
> >> Subject: Re: Not a v4.0.0 POM error
> >> From: nick.stolw...@gmail.com
> >> To: users@maven.apache.org
> >>
> >> What do you see if you open it with a browser:
> >>
> >> https://www.mycomp.com/maven2/repository/public/org/apache/maven/plugi
> >> ns/maven-install-plugin/2.3/maven-install-plugin-2.3.pom
> >>
> >> Is it a valid pom or some garble?
> >>
> >> With regards,
> >>
> >> Nick Stolwijk
> >> ~Java Developer~
> >>
> >> IPROFS BV.
> >> Claus Sluterweg 125
> >> 2012 WS Haarlem
> >> http://www.iprofs.nl
> >>
> >>
> >>
> >> On Thu, Nov 12, 2009 at 12:19 AM, Gerardo Corro  
> >> wrote:
> >> >
> >> > Hi,
> >> >
> >> > Thanks for your message, however is not working :-(  the same error is 
> >> > triggered again.
> >> >
> >> > Best regards
> >> >
> >> >
> >> >
> >> >
> >> >>
> >> >> I suggest you to delete the directory in your local repository
> >> >>
> >> >> /data/repository/org/apache/maven/plugins/maven-install-plugin/2.3/
> >> >>
> >> >> anyway, for me nothing to see with ubuntu (I works on it too)
> >> >>
> >> >> I already had such errors when a download of an artifact failed
> >> >> (for multiple reason...)
> >> >>
> >> >> hope it will help you.
> >> >>
> >> >> Cheers,
> >> >>
> >> >> Tony.
> >> >>
> >> >> >
> >> >> > [WARNING] *** CHECKSUM FAILED - Checksum failed on download:
> >> >> > local = 'e6084a3bb5d435dcb42378cd3273f5db433cb944'; remote = '
> >> >> > ' - RETRYING
> >> >> > Downloading:
> >> >> > https://www.mycomp.com/maven2/repository/public/org/apache/maven/
> >> >> > plugins/maven-install-plugin/2.3/maven-install-plugin-2.3.pom
> >> >> > 1K downloaded  (maven-install-plugin-2.3.pom) [WARNING] ***
> >> >> > CHECKSUM FAILED - Checksum failed on download: local =
> >> >> > 'e6084a3bb5d435dcb42378cd3273f5db433cb

RE: Not a v4.0.0 POM error

2009-11-12 Thread Gerardo Corro

Hi, 

If I do:


$ cat maven-install-plugin-2.3.pom 
�W[o�6~7���0d�
/mPc�Dn�>�-��H��|C��i�N'�
   
?Q��u��%�r�bp�e/o���/��Q�y^�wE�$I��H�8�G��j�A��b)V�
=ŗO,�...@��~tp�i8s��*ps�g(&�8��L��ќ�`�RY[A�U
 Р���Gsp�Ӕ��8G���0 
�=A2,t6��-�+/h
��:�C����<���x�w��d��...@tq��lmv�@3�A�$��+��J��A�Z�|l��\dA�Xp��į=��߲�H����j:�
 \��aHWU��4��T�e'��l��6e[���...@�0td0��8��f�8>A���77o�n4���]�L^  
  �.�h}��I� &_


seems like a binary file.

Thanks!!!


> From: shenne...@astutenetworks.com
> To: users@maven.apache.org
> Date: Wed, 11 Nov 2009 17:19:08 -0800
> Subject: RE: Not a v4.0.0 POM error
> 
> Pardon me but usually the .pom is an xml text file.
> you should be able to open w/ text editor on ubuntu.
> try using vi or gedit.
> 
> Sean
> 
> -Original Message-
> From: Gerardo Corro [mailto:rob_gar_...@hotmail.com] 
> Sent: Wednesday, November 11, 2009 5:11 PM
> To: users@maven.apache.org
> Subject: RE: Not a v4.0.0 POM error
> 
> 
> It's a valid pom:
> 
> $ ls -l maven-install-plugin-2.3.pom
> -rw-r--r-- 1 corro corro 1486 2009-11-12 01:33 maven-install-plugin-2.3.pom $ 
> file maven-install-plugin-2.3.pom
> maven-install-plugin-2.3.pom: gzip compressed data, from Unix $ gunzip -c  
> maven-install-plugin-2.3.pom   xmlns="http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/xsd/maven-4.0.0.xsd";>
>   4.0.0
> 
> and the file continues... however Ubuntu "Archive Manager Tool" can't extract 
> it, it says the pom has errors.
> 
> Best regards.
> 
> 
> > Date: Thu, 12 Nov 2009 01:21:26 +0100
> > Subject: Re: Not a v4.0.0 POM error
> > From: nick.stolw...@gmail.com
> > To: users@maven.apache.org
> > 
> > What do you see if you open it with a browser:
> > 
> > https://www.mycomp.com/maven2/repository/public/org/apache/maven/plugi
> > ns/maven-install-plugin/2.3/maven-install-plugin-2.3.pom
> > 
> > Is it a valid pom or some garble?
> > 
> > With regards,
> > 
> > Nick Stolwijk
> > ~Java Developer~
> > 
> > IPROFS BV.
> > Claus Sluterweg 125
> > 2012 WS Haarlem
> > http://www.iprofs.nl
> > 
> > 
> > 
> > On Thu, Nov 12, 2009 at 12:19 AM, Gerardo Corro  
> > wrote:
> > >
> > > Hi,
> > >
> > > Thanks for your message, however is not working :-(  the same error is 
> > > triggered again.
> > >
> > > Best regards
> > >
> > >
> > >
> > >
> > >>
> > >> I suggest you to delete the directory in your local repository
> > >>
> > >> /data/repository/org/apache/maven/plugins/maven-install-plugin/2.3/
> > >>
> > >> anyway, for me nothing to see with ubuntu (I works on it too)
> > >>
> > >> I already had such errors when a download of an artifact failed 
> > >> (for multiple reason...)
> > >>
> > >> hope it will help you.
> > >>
> > >> Cheers,
> > >>
> > >> Tony.
> > >>
> > >> >
> > >> > [WARNING] *** CHECKSUM FAILED - Checksum failed on download: 
> > >> > local = 'e6084a3bb5d435dcb42378cd3273f5db433cb944'; remote = '
> > >> > ' - RETRYING
> > >> > Downloading:
> > >> > https://www.mycomp.com/maven2/repository/public/org/apache/maven/
> > >> > plugins/maven-install-plugin/2.3/maven-install-plugin-2.3.pom
> > >> > 1K downloaded  (maven-install-plugin-2.3.pom) [WARNING] *** 
> > >> > CHECKSUM FAILED - Checksum failed on download: local = 
> > >> > 'e6084a3bb5d435dcb42378cd3273f5db433cb944'; remote = '' - 
> > >> > IGNORING [INFO]
> > >> > -
> > >> > ---
> > >> > [ERROR] BUILD ERROR [INFO]
> > >> > -
> > >> > --- [INFO] Error building POM (may not be this project's 
> > >> > POM).
> > >> >
> > >> >
> > >> > Project ID: org.apache.maven.plugins:maven-install-plugin
> >

Re: Not a v4.0.0 POM error

2009-11-11 Thread Nick Stolwijk
It is trying to get the remote file and that one (the link you
provided) does not work on my computer. It may be you have changed the
link in your mail, or it that it will let you in. But if you get the
same as me, then there is your problem. Who or what put the pom file
on the url you are pointing to? Is is some repository manager?

With regards,

Nick Stolwijk
~Java Developer~

IPROFS BV.
Claus Sluterweg 125
2012 WS Haarlem
http://www.iprofs.nl



On Thu, Nov 12, 2009 at 2:19 AM, Sean Hennessy
 wrote:
> Pardon me but usually the .pom is an xml text file.
> you should be able to open w/ text editor on ubuntu.
> try using vi or gedit.
>
> Sean
>
> -Original Message-
> From: Gerardo Corro [mailto:rob_gar_...@hotmail.com]
> Sent: Wednesday, November 11, 2009 5:11 PM
> To: users@maven.apache.org
> Subject: RE: Not a v4.0.0 POM error
>
>
> It's a valid pom:
>
> $ ls -l maven-install-plugin-2.3.pom
> -rw-r--r-- 1 corro corro 1486 2009-11-12 01:33 maven-install-plugin-2.3.pom $ 
> file maven-install-plugin-2.3.pom
> maven-install-plugin-2.3.pom: gzip compressed data, from Unix $ gunzip -c  
> maven-install-plugin-2.3.pom   xmlns="http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/xsd/maven-4.0.0.xsd";>
>  4.0.0
>
> and the file continues... however Ubuntu "Archive Manager Tool" can't extract 
> it, it says the pom has errors.
>
> Best regards.
>
>
>> Date: Thu, 12 Nov 2009 01:21:26 +0100
>> Subject: Re: Not a v4.0.0 POM error
>> From: nick.stolw...@gmail.com
>> To: users@maven.apache.org
>>
>> What do you see if you open it with a browser:
>>
>> https://www.mycomp.com/maven2/repository/public/org/apache/maven/plugi
>> ns/maven-install-plugin/2.3/maven-install-plugin-2.3.pom
>>
>> Is it a valid pom or some garble?
>>
>> With regards,
>>
>> Nick Stolwijk
>> ~Java Developer~
>>
>> IPROFS BV.
>> Claus Sluterweg 125
>> 2012 WS Haarlem
>> http://www.iprofs.nl
>>
>>
>>
>> On Thu, Nov 12, 2009 at 12:19 AM, Gerardo Corro  
>> wrote:
>> >
>> > Hi,
>> >
>> > Thanks for your message, however is not working :-(  the same error is 
>> > triggered again.
>> >
>> > Best regards
>> >
>> >
>> >
>> >
>> >>
>> >> I suggest you to delete the directory in your local repository
>> >>
>> >> /data/repository/org/apache/maven/plugins/maven-install-plugin/2.3/
>> >>
>> >> anyway, for me nothing to see with ubuntu (I works on it too)
>> >>
>> >> I already had such errors when a download of an artifact failed
>> >> (for multiple reason...)
>> >>
>> >> hope it will help you.
>> >>
>> >> Cheers,
>> >>
>> >> Tony.
>> >>
>> >> >
>> >> > [WARNING] *** CHECKSUM FAILED - Checksum failed on download:
>> >> > local = 'e6084a3bb5d435dcb42378cd3273f5db433cb944'; remote = '
>> >> > ' - RETRYING
>> >> > Downloading:
>> >> > https://www.mycomp.com/maven2/repository/public/org/apache/maven/
>> >> > plugins/maven-install-plugin/2.3/maven-install-plugin-2.3.pom
>> >> > 1K downloaded  (maven-install-plugin-2.3.pom) [WARNING] ***
>> >> > CHECKSUM FAILED - Checksum failed on download: local =
>> >> > 'e6084a3bb5d435dcb42378cd3273f5db433cb944'; remote = '    ' -
>> >> > IGNORING [INFO]
>> >> > -
>> >> > ---
>> >> > [ERROR] BUILD ERROR [INFO]
>> >> > -
>> >> > --- [INFO] Error building POM (may not be this project's
>> >> > POM).
>> >> >
>> >> >
>> >> > Project ID: org.apache.maven.plugins:maven-install-plugin
>> >> > POM
>> >> > Location:
>> >> > /data/repository/org/apache/maven/plugins/maven-install-plugin/2.
>> >> > 3/maven-install-plugin-2.3.pom
>> >> >
>> >> > Reason: Not a v4.0.0 POM. for project
>> >> > org.apache.maven.plugins:maven-install-plugin
>> >> > at
>> >> > /data/repository/

RE: Not a v4.0.0 POM error

2009-11-11 Thread Sean Hennessy
Pardon me but usually the .pom is an xml text file.
you should be able to open w/ text editor on ubuntu.
try using vi or gedit.

Sean

-Original Message-
From: Gerardo Corro [mailto:rob_gar_...@hotmail.com] 
Sent: Wednesday, November 11, 2009 5:11 PM
To: users@maven.apache.org
Subject: RE: Not a v4.0.0 POM error


It's a valid pom:

$ ls -l maven-install-plugin-2.3.pom
-rw-r--r-- 1 corro corro 1486 2009-11-12 01:33 maven-install-plugin-2.3.pom $ 
file maven-install-plugin-2.3.pom
maven-install-plugin-2.3.pom: gzip compressed data, from Unix $ gunzip -c  
maven-install-plugin-2.3.pom  http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd";>
  4.0.0

and the file continues... however Ubuntu "Archive Manager Tool" can't extract 
it, it says the pom has errors.

Best regards.


> Date: Thu, 12 Nov 2009 01:21:26 +0100
> Subject: Re: Not a v4.0.0 POM error
> From: nick.stolw...@gmail.com
> To: users@maven.apache.org
> 
> What do you see if you open it with a browser:
> 
> https://www.mycomp.com/maven2/repository/public/org/apache/maven/plugi
> ns/maven-install-plugin/2.3/maven-install-plugin-2.3.pom
> 
> Is it a valid pom or some garble?
> 
> With regards,
> 
> Nick Stolwijk
> ~Java Developer~
> 
> IPROFS BV.
> Claus Sluterweg 125
> 2012 WS Haarlem
> http://www.iprofs.nl
> 
> 
> 
> On Thu, Nov 12, 2009 at 12:19 AM, Gerardo Corro  
> wrote:
> >
> > Hi,
> >
> > Thanks for your message, however is not working :-(  the same error is 
> > triggered again.
> >
> > Best regards
> >
> >
> >
> >
> >>
> >> I suggest you to delete the directory in your local repository
> >>
> >> /data/repository/org/apache/maven/plugins/maven-install-plugin/2.3/
> >>
> >> anyway, for me nothing to see with ubuntu (I works on it too)
> >>
> >> I already had such errors when a download of an artifact failed 
> >> (for multiple reason...)
> >>
> >> hope it will help you.
> >>
> >> Cheers,
> >>
> >> Tony.
> >>
> >> >
> >> > [WARNING] *** CHECKSUM FAILED - Checksum failed on download: 
> >> > local = 'e6084a3bb5d435dcb42378cd3273f5db433cb944'; remote = '
> >> > ' - RETRYING
> >> > Downloading:
> >> > https://www.mycomp.com/maven2/repository/public/org/apache/maven/
> >> > plugins/maven-install-plugin/2.3/maven-install-plugin-2.3.pom
> >> > 1K downloaded  (maven-install-plugin-2.3.pom) [WARNING] *** 
> >> > CHECKSUM FAILED - Checksum failed on download: local = 
> >> > 'e6084a3bb5d435dcb42378cd3273f5db433cb944'; remote = '' - 
> >> > IGNORING [INFO]
> >> > ---------
> >> > ---
> >> > [ERROR] BUILD ERROR [INFO]
> >> > -
> >> > --- [INFO] Error building POM (may not be this project's 
> >> > POM).
> >> >
> >> >
> >> > Project ID: org.apache.maven.plugins:maven-install-plugin
> >> > POM
> >> > Location: 
> >> > /data/repository/org/apache/maven/plugins/maven-install-plugin/2.
> >> > 3/maven-install-plugin-2.3.pom
> >> >
> >> > Reason: Not a v4.0.0 POM. for project 
> >> > org.apache.maven.plugins:maven-install-plugin
> >> > at 
> >> > /data/repository/org/apache/maven/plugins/maven-install-plugin/2.
> >> > 3/maven-install-plugin-2.3.pom
> >> >
> >> >
> >> >
> >> > if using the -e version I get:
> >> >
> >> > [INFO]
> >> > -
> >> > --- [INFO] Trace 
> >> > org.apache.maven.lifecycle.LifecycleExecutionException: Unable to 
> >> > build project for plugin 'org.apache.maven.plugins:maven-install-plugin':
> >> > Not a v4.0.0 POM. for project 
> >> > org.apache.maven.plugins:maven-install-plugin
> >> > at 
> >> > /data/repository/org/apache/maven/plugins/maven-install-plugin/2.
> >> > 3/maven-install-plugin-2.3.pom
> >> > at
> >> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(
> >> > DefaultLifecycleE

RE: Not a v4.0.0 POM error

2009-11-11 Thread Gerardo Corro

It's a valid pom:

$ ls -l maven-install-plugin-2.3.pom 
-rw-r--r-- 1 corro corro 1486 2009-11-12 01:33 maven-install-plugin-2.3.pom
$ file maven-install-plugin-2.3.pom 
maven-install-plugin-2.3.pom: gzip compressed data, from Unix
$ gunzip -c  maven-install-plugin-2.3.pom

http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd";>
  4.0.0

and the file continues... however Ubuntu "Archive Manager Tool" can't extract 
it, it says the pom has errors.

Best regards.


> Date: Thu, 12 Nov 2009 01:21:26 +0100
> Subject: Re: Not a v4.0.0 POM error
> From: nick.stolw...@gmail.com
> To: users@maven.apache.org
> 
> What do you see if you open it with a browser:
> 
> https://www.mycomp.com/maven2/repository/public/org/apache/maven/plugins/maven-install-plugin/2.3/maven-install-plugin-2.3.pom
> 
> Is it a valid pom or some garble?
> 
> With regards,
> 
> Nick Stolwijk
> ~Java Developer~
> 
> IPROFS BV.
> Claus Sluterweg 125
> 2012 WS Haarlem
> http://www.iprofs.nl
> 
> 
> 
> On Thu, Nov 12, 2009 at 12:19 AM, Gerardo Corro  
> wrote:
> >
> > Hi,
> >
> > Thanks for your message, however is not working :-(  the same error is 
> > triggered again.
> >
> > Best regards
> >
> >
> >
> >
> >>
> >> I suggest you to delete the directory in your local repository
> >>
> >> /data/repository/org/apache/maven/plugins/maven-install-plugin/2.3/
> >>
> >> anyway, for me nothing to see with ubuntu (I works on it too)
> >>
> >> I already had such errors when a download of an artifact failed (for 
> >> multiple reason...)
> >>
> >> hope it will help you.
> >>
> >> Cheers,
> >>
> >> Tony.
> >>
> >> >
> >> > [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
> >> > 'e6084a3bb5d435dcb42378cd3273f5db433cb944'; remote = ' �� ' - RETRYING
> >> > Downloading:
> >> > https://www.mycomp.com/maven2/repository/public/org/apache/maven/plugins/maven-install-plugin/2.3/maven-install-plugin-2.3.pom
> >> > 1K downloaded  (maven-install-plugin-2.3.pom) [WARNING] *** CHECKSUM 
> >> > FAILED -
> >> > Checksum failed on download: local =
> >> > 'e6084a3bb5d435dcb42378cd3273f5db433cb944'; remote = ' �� ' - IGNORING 
> >> > [INFO]
> >> > 
> >> > [ERROR] BUILD ERROR [INFO]
> >> > 
> >> > [INFO] Error building POM (may not be this project's POM).
> >> >
> >> >
> >> > Project ID: org.apache.maven.plugins:maven-install-plugin
> >> > POM
> >> > Location: 
> >> > /data/repository/org/apache/maven/plugins/maven-install-plugin/2.3/maven-install-plugin-2.3.pom
> >> >
> >> > Reason: Not a v4.0.0 POM. for project
> >> > org.apache.maven.plugins:maven-install-plugin
> >> > at 
> >> > /data/repository/org/apache/maven/plugins/maven-install-plugin/2.3/maven-install-plugin-2.3.pom
> >> >
> >> >
> >> >
> >> > if using the -e version I get:
> >> >
> >> > [INFO]
> >> > 
> >> > [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: 
> >> > Unable
> >> > to build project for plugin 
> >> > 'org.apache.maven.plugins:maven-install-plugin':
> >> > Not a v4.0.0 POM. for project 
> >> > org.apache.maven.plugins:maven-install-plugin
> >> > at 
> >> > /data/repository/org/apache/maven/plugins/maven-install-plugin/2.3/maven-install-plugin-2.3.pom
> >> > at
> >> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1557)
> >> > at
> >> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1851)
> >> > at
> >> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindLifecycleForPackaging(DefaultLifecycleExecutor.java:1311)
> >> > at
> >> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappings(DefaultLifecycleExecutor.java:1275)
> >> >
>

RE: Not a v4.0.0 POM error

2009-11-11 Thread Martin Gainty

VERKEERDE PAGINA!

Martin 
__ 
Tevrden verander/wijzig of onderbreek deze transmissie niet - Bedankt


> Date: Thu, 12 Nov 2009 01:21:26 +0100
> Subject: Re: Not a v4.0.0 POM error
> From: nick.stolw...@gmail.com
> To: users@maven.apache.org
> 
> What do you see if you open it with a browser:
> 
> https://www.mycomp.com/maven2/repository/public/org/apache/maven/plugins/maven-install-plugin/2.3/maven-install-plugin-2.3.pom
> 
> Is it a valid pom or some garble?
> 
> With regards,
> 
> Nick Stolwijk
> ~Java Developer~
> 
> IPROFS BV.
> Claus Sluterweg 125
> 2012 WS Haarlem
> http://www.iprofs.nl
> 
> 
> 
> On Thu, Nov 12, 2009 at 12:19 AM, Gerardo Corro  
> wrote:
> >
> > Hi,
> >
> > Thanks for your message, however is not working :-(  the same error is 
> > triggered again.
> >
> > Best regards
> >
> >
> >
> >
> >>
> >> I suggest you to delete the directory in your local repository
> >>
> >> /data/repository/org/apache/maven/plugins/maven-install-plugin/2.3/
> >>
> >> anyway, for me nothing to see with ubuntu (I works on it too)
> >>
> >> I already had such errors when a download of an artifact failed (for 
> >> multiple reason...)
> >>
> >> hope it will help you.
> >>
> >> Cheers,
> >>
> >> Tony.
> >>
> >> >
> >> > [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
> >> > 'e6084a3bb5d435dcb42378cd3273f5db433cb944'; remote = ' �� ' - RETRYING
> >> > Downloading:
> >> > https://www.mycomp.com/maven2/repository/public/org/apache/maven/plugins/maven-install-plugin/2.3/maven-install-plugin-2.3.pom
> >> > 1K downloaded  (maven-install-plugin-2.3.pom) [WARNING] *** CHECKSUM 
> >> > FAILED -
> >> > Checksum failed on download: local =
> >> > 'e6084a3bb5d435dcb42378cd3273f5db433cb944'; remote = ' �� ' - IGNORING 
> >> > [INFO]
> >> > ----------------
> >> > [ERROR] BUILD ERROR [INFO]
> >> > 
> >> > [INFO] Error building POM (may not be this project's POM).
> >> >
> >> >
> >> > Project ID: org.apache.maven.plugins:maven-install-plugin
> >> > POM
> >> > Location: 
> >> > /data/repository/org/apache/maven/plugins/maven-install-plugin/2.3/maven-install-plugin-2.3.pom
> >> >
> >> > Reason: Not a v4.0.0 POM. for project
> >> > org.apache.maven.plugins:maven-install-plugin
> >> > at 
> >> > /data/repository/org/apache/maven/plugins/maven-install-plugin/2.3/maven-install-plugin-2.3.pom
> >> >
> >> >
> >> >
> >> > if using the -e version I get:
> >> >
> >> > [INFO]
> >> > 
> >> > [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: 
> >> > Unable
> >> > to build project for plugin 
> >> > 'org.apache.maven.plugins:maven-install-plugin':
> >> > Not a v4.0.0 POM. for project 
> >> > org.apache.maven.plugins:maven-install-plugin
> >> > at 
> >> > /data/repository/org/apache/maven/plugins/maven-install-plugin/2.3/maven-install-plugin-2.3.pom
> >> > at
> >> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1557)
> >> > at
> >> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1851)
> >> > at
> >> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindLifecycleForPackaging(DefaultLifecycleExecutor.java:1311)
> >> > at
> >> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappings(DefaultLifecycleExecutor.java:1275)
> >> >
> >> >
> >> >
> >> > Caused by: org.apache.maven.plugin.InvalidPluginException: Unable to 
> >> > build
> >> > project for plugin 'org.apache.maven.plugins:maven-install-plugin': Not a
> >> > v4.0.0 POM. for project org.apache.maven.plugins:maven-install-plugin
> >> > at 
> >> > /data/colibria/repository/org/apache/maven/plugins/maven-install-plugin/2.3

Re: Not a v4.0.0 POM error

2009-11-11 Thread Nick Stolwijk
What do you see if you open it with a browser:

https://www.mycomp.com/maven2/repository/public/org/apache/maven/plugins/maven-install-plugin/2.3/maven-install-plugin-2.3.pom

Is it a valid pom or some garble?

With regards,

Nick Stolwijk
~Java Developer~

IPROFS BV.
Claus Sluterweg 125
2012 WS Haarlem
http://www.iprofs.nl



On Thu, Nov 12, 2009 at 12:19 AM, Gerardo Corro  wrote:
>
> Hi,
>
> Thanks for your message, however is not working :-(  the same error is 
> triggered again.
>
> Best regards
>
>
>
>
>>
>> I suggest you to delete the directory in your local repository
>>
>> /data/repository/org/apache/maven/plugins/maven-install-plugin/2.3/
>>
>> anyway, for me nothing to see with ubuntu (I works on it too)
>>
>> I already had such errors when a download of an artifact failed (for 
>> multiple reason...)
>>
>> hope it will help you.
>>
>> Cheers,
>>
>> Tony.
>>
>> >
>> > [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
>> > 'e6084a3bb5d435dcb42378cd3273f5db433cb944'; remote = ' �� ' - RETRYING
>> > Downloading:
>> > https://www.mycomp.com/maven2/repository/public/org/apache/maven/plugins/maven-install-plugin/2.3/maven-install-plugin-2.3.pom
>> > 1K downloaded  (maven-install-plugin-2.3.pom) [WARNING] *** CHECKSUM 
>> > FAILED -
>> > Checksum failed on download: local =
>> > 'e6084a3bb5d435dcb42378cd3273f5db433cb944'; remote = ' �� ' - IGNORING 
>> > [INFO]
>> > 
>> > [ERROR] BUILD ERROR [INFO]
>> > ----
>> > [INFO] Error building POM (may not be this project's POM).
>> >
>> >
>> > Project ID: org.apache.maven.plugins:maven-install-plugin
>> > POM
>> > Location: 
>> > /data/repository/org/apache/maven/plugins/maven-install-plugin/2.3/maven-install-plugin-2.3.pom
>> >
>> > Reason: Not a v4.0.0 POM. for project
>> > org.apache.maven.plugins:maven-install-plugin
>> > at 
>> > /data/repository/org/apache/maven/plugins/maven-install-plugin/2.3/maven-install-plugin-2.3.pom
>> >
>> >
>> >
>> > if using the -e version I get:
>> >
>> > [INFO]
>> > 
>> > [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Unable
>> > to build project for plugin 
>> > 'org.apache.maven.plugins:maven-install-plugin':
>> > Not a v4.0.0 POM. for project org.apache.maven.plugins:maven-install-plugin
>> > at 
>> > /data/repository/org/apache/maven/plugins/maven-install-plugin/2.3/maven-install-plugin-2.3.pom
>> > at
>> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1557)
>> > at
>> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1851)
>> > at
>> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindLifecycleForPackaging(DefaultLifecycleExecutor.java:1311)
>> > at
>> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappings(DefaultLifecycleExecutor.java:1275)
>> >
>> >
>> >
>> > Caused by: org.apache.maven.plugin.InvalidPluginException: Unable to build
>> > project for plugin 'org.apache.maven.plugins:maven-install-plugin': Not a
>> > v4.0.0 POM. for project org.apache.maven.plugins:maven-install-plugin
>> > at 
>> > /data/colibria/repository/org/apache/maven/plugins/maven-install-plugin/2.3/maven-install-plugin-2.3.pom
>> > at
>> > org.apache.maven.plugin.DefaultPluginManager.checkRequiredMavenVersion(DefaultPluginManager.java:293)
>> > at
>> > org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(DefaultPluginManager.java:205)
>> >
>> >
>> >
>> > Please assist. Thanks!
>> >
>> >
>> >
>> >
>> >
>> >
>> > _
>> > Windows Live: Keep your friends up to date with what you do online.
>> > http://www.microsoft.com/middleeast/windows/windowslive/see-it-in-action/social-network-basics.aspx?ocid=PID23461::T:WLMTAGL:ON:WL:en-xm:SI_SB_1:092010
>>
>>
>> --
>>
>> Tony Chemit
>> 
>> tél: +33 (0) 2 40 50 29 28
>> email: che...@codelutin.com
>> http://www.codelutin.com
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> For additional commands, e-mail: users-h...@maven.apache.org
>>
>
> _
> Windows Live Hotmail: Your friends can get your Facebook updates, right from 
> Hotmail®.
> http://www.microsoft.com/middleeast/windows/windowslive/see-it-in-action/social-network-basics.aspx?ocid=PID23461::T:WLMTAGL:ON:WL:en-xm:SI_SB_4:092009

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



RE: Not a v4.0.0 POM error

2009-11-11 Thread Gerardo Corro

Hi,

Thanks for your message, however is not working :-(  the same error is 
triggered again.

Best regards




> 
> I suggest you to delete the directory in your local repository
> 
> /data/repository/org/apache/maven/plugins/maven-install-plugin/2.3/
> 
> anyway, for me nothing to see with ubuntu (I works on it too)
> 
> I already had such errors when a download of an artifact failed (for multiple 
> reason...)
> 
> hope it will help you.
> 
> Cheers,
> 
> Tony.
> 
> > 
> > [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
> > 'e6084a3bb5d435dcb42378cd3273f5db433cb944'; remote = '��' - RETRYING
> > Downloading:
> > https://www.mycomp.com/maven2/repository/public/org/apache/maven/plugins/maven-install-plugin/2.3/maven-install-plugin-2.3.pom
> > 1K downloaded  (maven-install-plugin-2.3.pom) [WARNING] *** CHECKSUM FAILED 
> > -
> > Checksum failed on download: local =
> > 'e6084a3bb5d435dcb42378cd3273f5db433cb944'; remote = '��' - IGNORING 
> > [INFO]
> > 
> > [ERROR] BUILD ERROR [INFO]
> > 
> > [INFO] Error building POM (may not be this project's POM).
> > 
> > 
> > Project ID: org.apache.maven.plugins:maven-install-plugin
> > POM
> > Location: 
> > /data/repository/org/apache/maven/plugins/maven-install-plugin/2.3/maven-install-plugin-2.3.pom
> > 
> > Reason: Not a v4.0.0 POM. for project
> > org.apache.maven.plugins:maven-install-plugin
> > at 
> > /data/repository/org/apache/maven/plugins/maven-install-plugin/2.3/maven-install-plugin-2.3.pom
> > 
> > 
> > 
> > if using the -e version I get:
> > 
> > [INFO]
> > 
> > [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Unable
> > to build project for plugin 'org.apache.maven.plugins:maven-install-plugin':
> > Not a v4.0.0 POM. for project org.apache.maven.plugins:maven-install-plugin
> > at 
> > /data/repository/org/apache/maven/plugins/maven-install-plugin/2.3/maven-install-plugin-2.3.pom
> > at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1557)
> > at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1851)
> > at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindLifecycleForPackaging(DefaultLifecycleExecutor.java:1311)
> > at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappings(DefaultLifecycleExecutor.java:1275)
> > 
> > 
> > 
> > Caused by: org.apache.maven.plugin.InvalidPluginException: Unable to build
> > project for plugin 'org.apache.maven.plugins:maven-install-plugin': Not a
> > v4.0.0 POM. for project org.apache.maven.plugins:maven-install-plugin
> > at 
> > /data/colibria/repository/org/apache/maven/plugins/maven-install-plugin/2.3/maven-install-plugin-2.3.pom
> > at
> > org.apache.maven.plugin.DefaultPluginManager.checkRequiredMavenVersion(DefaultPluginManager.java:293)
> > at
> > org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(DefaultPluginManager.java:205)
> > 
> > 
> > 
> > Please assist. Thanks!
> > 
> > 
> > 
> > 
> > 
> >   
> > _
> > Windows Live: Keep your friends up to date with what you do online.
> > http://www.microsoft.com/middleeast/windows/windowslive/see-it-in-action/social-network-basics.aspx?ocid=PID23461::T:WLMTAGL:ON:WL:en-xm:SI_SB_1:092010
> 
> 
> -- 
> 
> Tony Chemit
> 
> tél: +33 (0) 2 40 50 29 28
> email: che...@codelutin.com  
> http://www.codelutin.com 
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
> 
  
_
Windows Live Hotmail: Your friends can get your Facebook updates, right from 
Hotmail®.
http://www.microsoft.com/middleeast/windows/windowslive/see-it-in-action/social-network-basics.aspx?ocid=PID23461::T:WLMTAGL:ON:WL:en-xm:SI_SB_4:092009

Re: Not a v4.0.0 POM error

2009-11-11 Thread Tony Chemit
Le Wed, 11 Nov 2009 17:00:51 -0600,
Gerardo Corro  a écrit :

> 
> Hi all,
> 
> 
> Today, I was using Maven as usual in my Ubuntu laptop, then I decided to
> update Ubuntu to the 9.10 version, after that I tried to use maven as usual
> but now I get this error all the times I try to compile or install anything:
> 

I suggest you to delete the directory in your local repository

/data/repository/org/apache/maven/plugins/maven-install-plugin/2.3/

anyway, for me nothing to see with ubuntu (I works on it too)

I already had such errors when a download of an artifact failed (for multiple 
reason...)

hope it will help you.

Cheers,

Tony.

> 
> [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
> 'e6084a3bb5d435dcb42378cd3273f5db433cb944'; remote = '��' - RETRYING
> Downloading:
> https://www.mycomp.com/maven2/repository/public/org/apache/maven/plugins/maven-install-plugin/2.3/maven-install-plugin-2.3.pom
> 1K downloaded  (maven-install-plugin-2.3.pom) [WARNING] *** CHECKSUM FAILED -
> Checksum failed on download: local =
> 'e6084a3bb5d435dcb42378cd3273f5db433cb944'; remote = '��' - IGNORING [INFO]
> 
> [ERROR] BUILD ERROR [INFO]
> 
> [INFO] Error building POM (may not be this project's POM).
> 
> 
> Project ID: org.apache.maven.plugins:maven-install-plugin
> POM
> Location: 
> /data/repository/org/apache/maven/plugins/maven-install-plugin/2.3/maven-install-plugin-2.3.pom
> 
> Reason: Not a v4.0.0 POM. for project
> org.apache.maven.plugins:maven-install-plugin
> at 
> /data/repository/org/apache/maven/plugins/maven-install-plugin/2.3/maven-install-plugin-2.3.pom
> 
> 
> 
> if using the -e version I get:
> 
> [INFO]
> 
> [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Unable
> to build project for plugin 'org.apache.maven.plugins:maven-install-plugin':
> Not a v4.0.0 POM. for project org.apache.maven.plugins:maven-install-plugin
> at 
> /data/repository/org/apache/maven/plugins/maven-install-plugin/2.3/maven-install-plugin-2.3.pom
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1557)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1851)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindLifecycleForPackaging(DefaultLifecycleExecutor.java:1311)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappings(DefaultLifecycleExecutor.java:1275)
> 
> 
> 
> Caused by: org.apache.maven.plugin.InvalidPluginException: Unable to build
> project for plugin 'org.apache.maven.plugins:maven-install-plugin': Not a
> v4.0.0 POM. for project org.apache.maven.plugins:maven-install-plugin
> at 
> /data/colibria/repository/org/apache/maven/plugins/maven-install-plugin/2.3/maven-install-plugin-2.3.pom
> at
> org.apache.maven.plugin.DefaultPluginManager.checkRequiredMavenVersion(DefaultPluginManager.java:293)
> at
> org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(DefaultPluginManager.java:205)
> 
> 
> 
> Please assist. Thanks!
> 
> 
> 
> 
> 
> 
> _
> Windows Live: Keep your friends up to date with what you do online.
> http://www.microsoft.com/middleeast/windows/windowslive/see-it-in-action/social-network-basics.aspx?ocid=PID23461::T:WLMTAGL:ON:WL:en-xm:SI_SB_1:092010


-- 

Tony Chemit

tél: +33 (0) 2 40 50 29 28
email: che...@codelutin.com  
http://www.codelutin.com 

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Not a v4.0.0 POM error

2009-11-11 Thread Gerardo Corro

Hi all,


Today, I was using Maven as usual in my Ubuntu laptop, then I decided to update 
Ubuntu to the 9.10 version, after that I tried to use maven as usual but now I 
get this error all the times I try to compile or install anything:


[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = 
'e6084a3bb5d435dcb42378cd3273f5db433cb944'; remote = '��' - RETRYING
Downloading: 
https://www.mycomp.com/maven2/repository/public/org/apache/maven/plugins/maven-install-plugin/2.3/maven-install-plugin-2.3.pom
1K downloaded  (maven-install-plugin-2.3.pom)
[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = 
'e6084a3bb5d435dcb42378cd3273f5db433cb944'; remote = '��' - IGNORING
[INFO] 
[ERROR] BUILD ERROR
[INFO] 
[INFO] Error building POM (may not be this project's POM).


Project ID: org.apache.maven.plugins:maven-install-plugin
POM Location: 
/data/repository/org/apache/maven/plugins/maven-install-plugin/2.3/maven-install-plugin-2.3.pom

Reason: Not a v4.0.0 POM. for project 
org.apache.maven.plugins:maven-install-plugin at 
/data/repository/org/apache/maven/plugins/maven-install-plugin/2.3/maven-install-plugin-2.3.pom



if using the -e version I get:

[INFO] 
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Unable to build project 
for plugin 'org.apache.maven.plugins:maven-install-plugin': Not a v4.0.0 POM. 
for project org.apache.maven.plugins:maven-install-plugin at 
/data/repository/org/apache/maven/plugins/maven-install-plugin/2.3/maven-install-plugin-2.3.pom
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1557)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1851)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindLifecycleForPackaging(DefaultLifecycleExecutor.java:1311)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappings(DefaultLifecycleExecutor.java:1275)



Caused by: org.apache.maven.plugin.InvalidPluginException: Unable to build 
project for plugin 'org.apache.maven.plugins:maven-install-plugin': Not a 
v4.0.0 POM. for project org.apache.maven.plugins:maven-install-plugin at 
/data/colibria/repository/org/apache/maven/plugins/maven-install-plugin/2.3/maven-install-plugin-2.3.pom
at 
org.apache.maven.plugin.DefaultPluginManager.checkRequiredMavenVersion(DefaultPluginManager.java:293)
at 
org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(DefaultPluginManager.java:205)



Please assist. Thanks!





  
_
Windows Live: Keep your friends up to date with what you do online.
http://www.microsoft.com/middleeast/windows/windowslive/see-it-in-action/social-network-basics.aspx?ocid=PID23461::T:WLMTAGL:ON:WL:en-xm:SI_SB_1:092010

Re: Not a v4.0.0 POM

2008-10-13 Thread Wayne Fay
   testGwt
>
>
>
>
>
>org.apache.maven.plugins
>maven-war-plugin
>2.0
>
>target/web.xml
>
>
>
>
> 
>
> Do you know how it will compile?
> The tracktraces you can see here:
>
> + Error stacktraces are turned on.
> [INFO] Scanning for projects...
> [INFO] Searching repository for plugin with prefix: 'gwt'.
> [WARNING] Cannot resolve plugin-mapping metadata for groupId: 
> org.apache.maven.plugins - IGNORING.
> [WARNING] Cannot resolve plugin-mapping metadata for groupId: 
> org.codehaus.mojo - IGNORING.
> [INFO] 
> 
> [ERROR] BUILD ERROR
> [INFO] 
> 
> [INFO] Error building POM (may not be this project's POM).
>
> Project ID: org.apache.maven.plugins:maven-compiler-plugin
> POM Location: 
> C:\Users\I056462\.m2\repository\org\apache\maven\plugins\maven-compiler-plugin\2.0\maven-compiler-plugin-2.0.pom
>
> Reason: Not a v4.0.0 POM. for project 
> org.apache.maven.plugins:maven-compiler-plugin at 
> C:\Users\I056462\.m2\repository\org\apache\maven\plugins\maven-compiler-plugin\2.0\maven-compiler-plugin-2.0.pom
>
> [INFO] 
> 
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: Unable to build 
> project for plugin 'org.apache.maven.plugins:maven-compiler-plugin': Not a 
> v4.0.0 POM. for project org.apache.maven.plugins:maven-compiler-plugin at 
> C:\Users\I056462\.m2\repository\org\apache\maven\plugins\maven-compiler-plugin\2.0\maven-compiler-plugin-2.0.pom
>at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1291)
>at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1486)
>at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.segmentTaskListBy 
> AggregationNeeds(DefaultLifecycleExecutor.java:405)
>at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:137)
>at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
>at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
>at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
>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:597)
>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.InvalidPluginException: Unable to build 
> project for plugin 'org.apache.maven.plugins:maven-compiler-plugin': Not a 
> v4.0.0 POM. for project org.apache.maven.plugins:maven-compiler-plugin at 
> C:\Users\user\.m\repository\org\apache\maven\plugins\maven-compiler-plugin\2.0\maven-compiler-plugin-2.0.pom
>at 
> org.apache.maven.plugin.DefaultPluginManager.checkRequiredMavenVersion(DefaultPluginManager.java:281)
>at 
> org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(DefaultPluginManager.java:197)
>at 
> org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:176)
>at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1274)
>... 14 more
> Caused by: org.apache.maven.project.InvalidProjectModelException: Not a 
> v4.0.0 POM. for project org.apache.maven.plugins:maven-compiler-plugin at 
> C:\Users\I0564
> 62\.m2\repository\org\apache\maven\plugins\maven-compiler-plugin\2.0\maven-compi
> ler-plugin-2.0.pom
>at 
> org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMavenProjectBuilder.java:1581)
>at 
> org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMavenProjectBuilder.java:1553)
>at 
> org.apache.maven.project.DefaultMav

Not a v4.0.0 POM

2008-10-13 Thread tonqa
---
[ERROR] BUILD ERROR
[INFO] 
[INFO] Error building POM (may not be this project's POM).

Project ID: org.apache.maven.plugins:maven-compiler-plugin
POM Location: 
C:\Users\I056462\.m2\repository\org\apache\maven\plugins\maven-compiler-plugin\2.0\maven-compiler-plugin-2.0.pom

Reason: Not a v4.0.0 POM. for project 
org.apache.maven.plugins:maven-compiler-plugin at 
C:\Users\I056462\.m2\repository\org\apache\maven\plugins\maven-compiler-plugin\2.0\maven-compiler-plugin-2.0.pom

[INFO] 
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Unable to build project 
for plugin 'org.apache.maven.plugins:maven-compiler-plugin': Not a v4.0.0 POM. 
for project org.apache.maven.plugins:maven-compiler-plugin at 
C:\Users\I056462\.m2\repository\org\apache\maven\plugins\maven-compiler-plugin\2.0\maven-compiler-plugin-2.0.pom
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1291)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1486)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.segmentTaskListBy 
AggregationNeeds(DefaultLifecycleExecutor.java:405)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:137)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
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:597)
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.InvalidPluginException: Unable to build 
project for plugin 'org.apache.maven.plugins:maven-compiler-plugin': Not a 
v4.0.0 POM. for project org.apache.maven.plugins:maven-compiler-plugin at 
C:\Users\user\.m\repository\org\apache\maven\plugins\maven-compiler-plugin\2.0\maven-compiler-plugin-2.0.pom
at 
org.apache.maven.plugin.DefaultPluginManager.checkRequiredMavenVersion(DefaultPluginManager.java:281)
at 
org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(DefaultPluginManager.java:197)
at 
org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:176)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1274)
... 14 more
Caused by: org.apache.maven.project.InvalidProjectModelException: Not a v4.0.0 
POM. for project org.apache.maven.plugins:maven-compiler-plugin at 
C:\Users\I0564
62\.m2\repository\org\apache\maven\plugins\maven-compiler-plugin\2.0\maven-compi
ler-plugin-2.0.pom
at 
org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMavenProjectBuilder.java:1581)
at 
org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMavenProjectBuilder.java:1553)
at 
org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:560)
at 
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:249)
at 
org.apache.maven.plugin.DefaultPluginManager.checkRequiredMavenVersion(DefaultPluginManager.java:265)
... 17 more
[INFO] 
[INFO] Total time: < 1 second
[INFO] Finished at: Mon Oct 13 22:02:29 EST 2008
[INFO] Final Memory: 1M/254M
[INFO] 
-- 
Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! 
Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: Assembly problem: Error "Not a v4.0.0 POM"

2007-07-11 Thread Chris Helck
Hi John,

Thanks for the reply. I tried using the snapshot version, but still get
an error. First I added the following lines to my POM

 

  org.apache.maven.plugins
  maven-assembly-plugin
  2.2-beta-2-SNAPSHOT
  plugin

 

  

  
true
  
  central-snaps
  Maven Repository Snaps
  http://people.apache.org/repo/m2-snapshot-repository

  

  

  
never
  
  
true
  
  central-plugin-snaps
  Maven snap Plugin Repository
  http://people.apache.org/repo/m2-snapshot-repository

   

Everything seemed to download ok. When I ran (with -X) I get this stack
trace:

[INFO]

[DEBUG] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to create
assembly: Error retrieving POM of module-dependency:
ebs:commons:jar:3.0.5-SNAPSHOT; Reason: Not a v4.0.0 POM.
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default
LifecycleExecutor.java:559)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifec
ycle(DefaultLifecycleExecutor.java:475)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultL
ifecycleExecutor.java:454)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle
Failures(DefaultLifecycleExecutor.java:306)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
DefaultLifecycleExecutor.java:273)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec
ycleExecutor.java:140)
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.jav
a:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.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)
Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to
create assembly: Error retrieving POM of module-dependency:
ebs:commons:jar:3.0.5-SNAPSHOT; Reason: Not a v4.0.0 POM.
at
org.apache.maven.plugin.assembly.mojos.AbstractAssemblyMojo.execute(Abst
ractAssemblyMojo.java:302)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMa
nager.java:412)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default
LifecycleExecutor.java:534)
... 16 more
Caused by:
org.apache.maven.plugin.assembly.archive.ArchiveCreationException: Error
retrieving POM of module-dependency: ebs:commons:jar:3.0.5-SNAPSHOT;
Reason: Not a v4.0.0 POM.
at
org.apache.maven.plugin.assembly.archive.task.AddDependencySetsTask.addD
ependencySet(AddDependencySetsTask.java:115)
at
org.apache.maven.plugin.assembly.archive.task.AddDependencySetsTask.exec
ute(AddDependencySetsTask.java:91)
at
org.apache.maven.plugin.assembly.archive.phase.DependencySetAssemblyPhas
e.execute(DependencySetAssemblyPhase.java:54)
at
org.apache.maven.plugin.assembly.archive.DefaultAssemblyArchiver.createA
rchive(DefaultAssemblyArchiver.java:98)
at
org.apache.maven.plugin.assembly.mojos.AbstractAssemblyMojo.execute(Abst
ractAssemblyMojo.java:278)
... 18 more
Caused by: org.apache.maven.project.InvalidProjectModelException: Not a
v4.0.0 POM.
at
org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMav
enProjectBuilder.java:1299)
at
org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMav
enProjectBuilder.java:1270)
at
org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromReposit
ory(DefaultMavenProjectBuilder.java:471)
at
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(
DefaultMavenProjectBuilder.java:225)
at
org.apache.maven.plugin.assembly.archive.task.AddDependencySetsTask.addD
ependencySet(AddDependencySetsTask.java:110)
... 22 more
[INFO]

[INFO] Total time: 24 seconds
[INFO] Finished at: Wed Jul 11 10:39:43 EDT 2007
[INFO] Final Memory: 8M/16M
[INFO]


Regards,
Christopher Helck

[snip]

**
This communication and all information (including, but not limited to,
 market prices/levels

Re: Assembly problem: Error "Not a v4.0.0 POM"

2007-07-11 Thread George Armhold

I just tried the 2.2-beta-2-SNAPSHOT from that repo, and unfortunately the
problem still exists.

George



John Casey-5 wrote:
> 
> You two should try the snapshot of the assembly plugin on the  
> repository:
> 
> http://people.apache.org/repo/m2-snapshot-repository
> 
> While it's not great practice to load plugins from here, you can  
> verify that this problem has been fixed already. It's just not quite  
> ready for release, due to some other issues that need fixing still.
> 
> -john
> 
> 
> On Jul 11, 2007, at 9:31 AM, Chris Helck wrote:
> 
>> Hi George,
>>
>> I created an issue for this in jira
>> (http://jira.codehaus.org/browse/MASSEMBLY-225). Perhaps voting for it
>> would help?
>>
>> Regards,
>> Christopher
>>
>> -Original Message-
>> From: George Armhold [mailto:[EMAIL PROTECTED]
>> Sent: Monday, July 09, 2007 7:49 PM
>> To: users@maven.apache.org
>> Subject: RE: Assembly problem: Error "Not a v4.0.0 POM"
>>
>>
>> Hi John,
>>
>> I'm also interested in this fix for the assembly plugin.  Could you
>> kindly commit it, or at least post it here so we can apply it locally?
>>
>> Thanks,
>> George
>>
>>
>>
>> Chris Helck wrote:
>>>
>>> Was this ever fixed? I still see it in maven 2.0.6 -- am about to try
>>> with 2.0.7. I don't see any direct mention of the problem in the jira
>>> thingy.
>>>
>>> Thanks,
>>> Christopher Helck
>>>
>>>
>>> -Original Message-
>>> From: John Casey [mailto:[EMAIL PROTECTED]
>>> Sent: Tuesday, May 08, 2007 3:53 PM
>>> To: Maven Users List
>>> Subject: Re: Assembly problem: Error "Not a v4.0.0 POM"
>>>
>>> Okay, I've found the problem; it's in the assembly plugin, where I'm
>>> not using the correct method to retrieve the transitive POM set  
>>> (there
>>
>>> is one that allows "stub" models when it detects a non-4.0.0 POM, and
>>> another that doesn't). I'm fixing it now, but it won't be released  
>>> for
>>
>>> a little while (there are several more things that need to go into
>>> that release).
>>>
>>> Thanks, and sorry for the inconvenience.
>>>
>>> -john
>>>
>>> On 5/8/07, Chris Helck <[EMAIL PROTECTED]> wrote:
>>>>
>>>> I'm using maven 2.0.4. Assembly plugin is 2.2-beta-1.
>>>>
>>>> I'll be happy to supply more data it needed. Stack trace is below.
>>>>
>>>> Thanks,
>>>> Christopher Helck
>>>>
>>>>
>>>>
>>>> [INFO]
>>>>  
>>>> -
>>>> -
>>>> --
>>>> [DEBUG] Trace
>>>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
>>>> create
>>>> assembly: Error retrieving POM of module-dependency:
>>>> ebs:pps:jar:3.0.2;
>>>> Reason: Not a v4.0.0 POM.
>>>> at
>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals 
>>>> (Defa
>>>> u
>>>> lt
>>>> LifecycleExecutor.java:559)
>>>> at
>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithL 
>>>> i
>>>> f
>>>> ec
>>>> ycle(DefaultLifecycleExecutor.java:475)
>>>> at
>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal 
>>>> (Defau
>>>> l
>>>> tL
>>>> ifecycleExecutor.java:454)
>>>> at
>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHa 
>>>> n
>>>> d
>>>> le
>>>> Failures(DefaultLifecycleExecutor.java:306)
>>>> at
>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegme 
>>>> n
>>>> t
>>>> s(
>>>> DefaultLifecycleExecutor.java:273)
>>>> at
>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute 
>>>> (DefaultLi
>>>> f
>>>> ec
>>>> ycleExecutor.java:140)
>>>> at
>>>> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
>>>> at
>>> org.apache.maven.DefaultMaven.execute(DefaultMave

RE: Assembly problem: Error "Not a v4.0.0 POM"

2007-07-11 Thread George Armhold

Thanks Chris, I have voted for it.

George



Chris Helck wrote:
> 
> Hi George,
> 
> I created an issue for this in jira
> (http://jira.codehaus.org/browse/MASSEMBLY-225). Perhaps voting for it
> would help? 
> 
> Regards,
> Christopher 
> 
> -Original Message-
> From: George Armhold [mailto:[EMAIL PROTECTED] 
> Sent: Monday, July 09, 2007 7:49 PM
> To: users@maven.apache.org
> Subject: RE: Assembly problem: Error "Not a v4.0.0 POM"
> 
> 
> Hi John,
> 
> I'm also interested in this fix for the assembly plugin.  Could you
> kindly commit it, or at least post it here so we can apply it locally?
> 
> Thanks,
> George
> 
> 
> 
> Chris Helck wrote:
>> 
>> Was this ever fixed? I still see it in maven 2.0.6 -- am about to try 
>> with 2.0.7. I don't see any direct mention of the problem in the jira 
>> thingy.
>> 
>> Thanks,
>> Christopher Helck
>>  
>> 
>> -Original Message-
>> From: John Casey [mailto:[EMAIL PROTECTED]
>> Sent: Tuesday, May 08, 2007 3:53 PM
>> To: Maven Users List
>> Subject: Re: Assembly problem: Error "Not a v4.0.0 POM"
>> 
>> Okay, I've found the problem; it's in the assembly plugin, where I'm 
>> not using the correct method to retrieve the transitive POM set (there
> 
>> is one that allows "stub" models when it detects a non-4.0.0 POM, and 
>> another that doesn't). I'm fixing it now, but it won't be released for
> 
>> a little while (there are several more things that need to go into 
>> that release).
>> 
>> Thanks, and sorry for the inconvenience.
>> 
>> -john
>> 
>> On 5/8/07, Chris Helck <[EMAIL PROTECTED]> wrote:
>>>
>>> I'm using maven 2.0.4. Assembly plugin is 2.2-beta-1.
>>>
>>> I'll be happy to supply more data it needed. Stack trace is below.
>>>
>>> Thanks,
>>> Christopher Helck
>>>
>>>
>>>
>>> [INFO]
>>> -
>>> -
>>> --
>>> [DEBUG] Trace
>>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to 
>>> create
>>> assembly: Error retrieving POM of module-dependency: 
>>> ebs:pps:jar:3.0.2;
>>> Reason: Not a v4.0.0 POM.
>>> at
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
>>> u
>>> lt
>>> LifecycleExecutor.java:559)
>>> at
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
>>> f
>>> ec
>>> ycle(DefaultLifecycleExecutor.java:475)
>>> at
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
>>> l
>>> tL
>>> ifecycleExecutor.java:454)
>>> at
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
>>> d
>>> le
>>> Failures(DefaultLifecycleExecutor.java:306)
>>> at
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
>>> t
>>> s(
>>> DefaultLifecycleExecutor.java:273)
>>> at
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
>>> f
>>> ec
>>> ycleExecutor.java:140)
>>> 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.
>>> j
>>> av
>>> a:39)
>>> at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
>>> s
>>> or
>>> Impl.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)
>>> Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to 
>>>

Re: Assembly problem: Error "Not a v4.0.0 POM"

2007-07-11 Thread John Casey
You two should try the snapshot of the assembly plugin on the  
repository:


http://people.apache.org/repo/m2-snapshot-repository

While it's not great practice to load plugins from here, you can  
verify that this problem has been fixed already. It's just not quite  
ready for release, due to some other issues that need fixing still.


-john


On Jul 11, 2007, at 9:31 AM, Chris Helck wrote:


Hi George,

I created an issue for this in jira
(http://jira.codehaus.org/browse/MASSEMBLY-225). Perhaps voting for it
would help?

Regards,
Christopher

-Original Message-
From: George Armhold [mailto:[EMAIL PROTECTED]
Sent: Monday, July 09, 2007 7:49 PM
To: users@maven.apache.org
Subject: RE: Assembly problem: Error "Not a v4.0.0 POM"


Hi John,

I'm also interested in this fix for the assembly plugin.  Could you
kindly commit it, or at least post it here so we can apply it locally?

Thanks,
George



Chris Helck wrote:


Was this ever fixed? I still see it in maven 2.0.6 -- am about to try
with 2.0.7. I don't see any direct mention of the problem in the jira
thingy.

Thanks,
Christopher Helck


-Original Message-
From: John Casey [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 08, 2007 3:53 PM
To: Maven Users List
Subject: Re: Assembly problem: Error "Not a v4.0.0 POM"

Okay, I've found the problem; it's in the assembly plugin, where I'm
not using the correct method to retrieve the transitive POM set  
(there



is one that allows "stub" models when it detects a non-4.0.0 POM, and
another that doesn't). I'm fixing it now, but it won't be released  
for



a little while (there are several more things that need to go into
that release).

Thanks, and sorry for the inconvenience.

-john

On 5/8/07, Chris Helck <[EMAIL PROTECTED]> wrote:


I'm using maven 2.0.4. Assembly plugin is 2.2-beta-1.

I'll be happy to supply more data it needed. Stack trace is below.

Thanks,
Christopher Helck



[INFO]
 
-

-
--
[DEBUG] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
create
assembly: Error retrieving POM of module-dependency:
ebs:pps:jar:3.0.2;
Reason: Not a v4.0.0 POM.
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals 
(Defa

u
lt
LifecycleExecutor.java:559)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithL 
i

f
ec
ycle(DefaultLifecycleExecutor.java:475)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal 
(Defau

l
tL
ifecycleExecutor.java:454)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHa 
n

d
le
Failures(DefaultLifecycleExecutor.java:306)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegme 
n

t
s(
DefaultLifecycleExecutor.java:273)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute 
(DefaultLi

f
ec
ycleExecutor.java:140)
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.

j
av
a:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke 
(DelegatingMethodAcces

s
or
Impl.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)
Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to
create assembly: Error retrieving POM of module-dependency:
ebs:pps:jar:3.0.2; Reason: Not a v4.0.0 POM.
at
org.apache.maven.plugin.assembly.mojos.AbstractAssemblyMojo.execute( 
A

b
st
ractAssemblyMojo.java:302)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo 
(DefaultPlugi

n
Ma
nager.java:412)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals 
(Defa

u
lt
LifecycleExecutor.java:534)
... 16 more
Caused by:
org.apache.maven.plugin.assembly.archive.ArchiveCreationException:
Error retrieving POM of module-dependency: ebs:pps:jar:3.0.2;  
Reason:



Not a v4.0.0 POM.
at
org.apache.maven.plugin.assembly.archive.task.AddDependencySetsTask. 
a

d
dD
ependencySet(AddDependencySetsTask.java:114)
at
org.apache.maven.plugin.assembly.archive.task.AddDependencySetsTask. 
e

x
ec
ute(AddDependencySetsTask.java:90)
at
org.apache.maven.plugin.assembly.archive.phase.DependencySetAssembly 
P

h
as
e.execute(DependencySetAssemblyPhase.java:54)
at
org.apache.maven.plu

RE: Assembly problem: Error "Not a v4.0.0 POM"

2007-07-11 Thread Chris Helck
Hi George,

I created an issue for this in jira
(http://jira.codehaus.org/browse/MASSEMBLY-225). Perhaps voting for it
would help? 

Regards,
Christopher 

-Original Message-
From: George Armhold [mailto:[EMAIL PROTECTED] 
Sent: Monday, July 09, 2007 7:49 PM
To: users@maven.apache.org
Subject: RE: Assembly problem: Error "Not a v4.0.0 POM"


Hi John,

I'm also interested in this fix for the assembly plugin.  Could you
kindly commit it, or at least post it here so we can apply it locally?

Thanks,
George



Chris Helck wrote:
> 
> Was this ever fixed? I still see it in maven 2.0.6 -- am about to try 
> with 2.0.7. I don't see any direct mention of the problem in the jira 
> thingy.
> 
> Thanks,
> Christopher Helck
>  
> 
> -Original Message-
> From: John Casey [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, May 08, 2007 3:53 PM
> To: Maven Users List
> Subject: Re: Assembly problem: Error "Not a v4.0.0 POM"
> 
> Okay, I've found the problem; it's in the assembly plugin, where I'm 
> not using the correct method to retrieve the transitive POM set (there

> is one that allows "stub" models when it detects a non-4.0.0 POM, and 
> another that doesn't). I'm fixing it now, but it won't be released for

> a little while (there are several more things that need to go into 
> that release).
> 
> Thanks, and sorry for the inconvenience.
> 
> -john
> 
> On 5/8/07, Chris Helck <[EMAIL PROTECTED]> wrote:
>>
>> I'm using maven 2.0.4. Assembly plugin is 2.2-beta-1.
>>
>> I'll be happy to supply more data it needed. Stack trace is below.
>>
>> Thanks,
>> Christopher Helck
>>
>>
>>
>> [INFO]
>> -------------
>> -
>> --
>> [DEBUG] Trace
>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to 
>> create
>> assembly: Error retrieving POM of module-dependency: 
>> ebs:pps:jar:3.0.2;
>> Reason: Not a v4.0.0 POM.
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
>> u
>> lt
>> LifecycleExecutor.java:559)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
>> f
>> ec
>> ycle(DefaultLifecycleExecutor.java:475)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
>> l
>> tL
>> ifecycleExecutor.java:454)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
>> d
>> le
>> Failures(DefaultLifecycleExecutor.java:306)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
>> t
>> s(
>> DefaultLifecycleExecutor.java:273)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
>> f
>> ec
>> ycleExecutor.java:140)
>> 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.
>> j
>> av
>> a:39)
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
>> s
>> or
>> Impl.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)
>> Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to 
>> create assembly: Error retrieving POM of module-dependency:
>> ebs:pps:jar:3.0.2; Reason: Not a v4.0.0 POM.
>> at
>> org.apache.maven.plugin.assembly.mojos.AbstractAssemblyMojo.execute(A
>> b
>> st
>> ractAssemblyMojo.java:302)
>> at
>> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
>> n
>> Ma
>> nager.java:412)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
>> u
>> lt
>> LifecycleExecutor.java:534)
>> ... 16 more
>> Caused by:
>> org.apache.maven.p

RE: Assembly problem: Error "Not a v4.0.0 POM"

2007-07-09 Thread George Armhold

Hi John,

I'm also interested in this fix for the assembly plugin.  Could you kindly
commit it, or at least post it here so we can apply it locally?

Thanks,
George



Chris Helck wrote:
> 
> Was this ever fixed? I still see it in maven 2.0.6 -- am about to try
> with 2.0.7. I don't see any direct mention of the problem in the jira
> thingy.
> 
> Thanks,
> Christopher Helck
>  
> 
> -Original Message-
> From: John Casey [mailto:[EMAIL PROTECTED] 
> Sent: Tuesday, May 08, 2007 3:53 PM
> To: Maven Users List
> Subject: Re: Assembly problem: Error "Not a v4.0.0 POM"
> 
> Okay, I've found the problem; it's in the assembly plugin, where I'm not
> using the correct method to retrieve the transitive POM set (there is
> one that allows "stub" models when it detects a non-4.0.0 POM, and
> another that doesn't). I'm fixing it now, but it won't be released for a
> little while (there are several more things that need to go into that
> release).
> 
> Thanks, and sorry for the inconvenience.
> 
> -john
> 
> On 5/8/07, Chris Helck <[EMAIL PROTECTED]> wrote:
>>
>> I'm using maven 2.0.4. Assembly plugin is 2.2-beta-1.
>>
>> I'll be happy to supply more data it needed. Stack trace is below.
>>
>> Thanks,
>> Christopher Helck
>>
>>
>>
>> [INFO]
>> ------------------
>> --
>> [DEBUG] Trace
>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to 
>> create
>> assembly: Error retrieving POM of module-dependency: 
>> ebs:pps:jar:3.0.2;
>> Reason: Not a v4.0.0 POM.
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defau
>> lt
>> LifecycleExecutor.java:559)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLif
>> ec
>> ycle(DefaultLifecycleExecutor.java:475)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defaul
>> tL
>> ifecycleExecutor.java:454)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHand
>> le
>> Failures(DefaultLifecycleExecutor.java:306)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegment
>> s(
>> DefaultLifecycleExecutor.java:273)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLif
>> ec
>> ycleExecutor.java:140)
>> 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.j
>> av
>> a:39)
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccess
>> or
>> Impl.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)
>> Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to 
>> create assembly: Error retrieving POM of module-dependency:
>> ebs:pps:jar:3.0.2; Reason: Not a v4.0.0 POM.
>> at
>> org.apache.maven.plugin.assembly.mojos.AbstractAssemblyMojo.execute(Ab
>> st
>> ractAssemblyMojo.java:302)
>> at
>> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugin
>> Ma
>> nager.java:412)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defau
>> lt
>> LifecycleExecutor.java:534)
>> ... 16 more
>> Caused by:
>> org.apache.maven.plugin.assembly.archive.ArchiveCreationException: 
>> Error retrieving POM of module-dependency: ebs:pps:jar:3.0.2; Reason: 
>> Not a v4.0.0 POM.
>> at
>> org.apache.maven.plugin.assembly.archive.task.AddDependencySetsTask.ad
>> dD
>> ependencySet(AddDependencySetsTask.java:114)
>> at
>> org.apache.maven.plugin.assembly.archive.task.AddDependencySetsTask.ex
>> ec
>> ute(AddDependencySetsTask.java:90)
>> at
>> org.apache.maven.plugin.as

RE: Assembly problem: Error "Not a v4.0.0 POM"

2007-06-25 Thread Chris Helck
Was this ever fixed? I still see it in maven 2.0.6 -- am about to try
with 2.0.7. I don't see any direct mention of the problem in the jira
thingy.

Thanks,
Christopher Helck
 

-Original Message-
From: John Casey [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, May 08, 2007 3:53 PM
To: Maven Users List
Subject: Re: Assembly problem: Error "Not a v4.0.0 POM"

Okay, I've found the problem; it's in the assembly plugin, where I'm not
using the correct method to retrieve the transitive POM set (there is
one that allows "stub" models when it detects a non-4.0.0 POM, and
another that doesn't). I'm fixing it now, but it won't be released for a
little while (there are several more things that need to go into that
release).

Thanks, and sorry for the inconvenience.

-john

On 5/8/07, Chris Helck <[EMAIL PROTECTED]> wrote:
>
> I'm using maven 2.0.4. Assembly plugin is 2.2-beta-1.
>
> I'll be happy to supply more data it needed. Stack trace is below.
>
> Thanks,
> Christopher Helck
>
>
>
> [INFO]
> --
> --
> [DEBUG] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to 
> create
> assembly: Error retrieving POM of module-dependency: 
> ebs:pps:jar:3.0.2;
> Reason: Not a v4.0.0 POM.
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defau
> lt
> LifecycleExecutor.java:559)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLif
> ec
> ycle(DefaultLifecycleExecutor.java:475)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defaul
> tL
> ifecycleExecutor.java:454)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHand
> le
> Failures(DefaultLifecycleExecutor.java:306)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegment
> s(
> DefaultLifecycleExecutor.java:273)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLif
> ec
> ycleExecutor.java:140)
> 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.j
> av
> a:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccess
> or
> Impl.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)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to 
> create assembly: Error retrieving POM of module-dependency:
> ebs:pps:jar:3.0.2; Reason: Not a v4.0.0 POM.
> at
> org.apache.maven.plugin.assembly.mojos.AbstractAssemblyMojo.execute(Ab
> st
> ractAssemblyMojo.java:302)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugin
> Ma
> nager.java:412)
>     at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defau
> lt
> LifecycleExecutor.java:534)
> ... 16 more
> Caused by:
> org.apache.maven.plugin.assembly.archive.ArchiveCreationException: 
> Error retrieving POM of module-dependency: ebs:pps:jar:3.0.2; Reason: 
> Not a v4.0.0 POM.
> at
> org.apache.maven.plugin.assembly.archive.task.AddDependencySetsTask.ad
> dD
> ependencySet(AddDependencySetsTask.java:114)
> at
> org.apache.maven.plugin.assembly.archive.task.AddDependencySetsTask.ex
> ec
> ute(AddDependencySetsTask.java:90)
> at
> org.apache.maven.plugin.assembly.archive.phase.DependencySetAssemblyPh
> as
> e.execute(DependencySetAssemblyPhase.java:54)
>     at
> org.apache.maven.plugin.assembly.archive.DefaultAssemblyArchiver.creat
> eA
> rchive(DefaultAssemblyArchiver.java:98)
> at
> org.apache.maven.plugin.assembly.mojos.AbstractAssemblyMojo.execute(Ab
> st
> ractAssemblyMojo.java:278)
> ... 18 more
> Caused by: org.apache.maven.project.InvalidProjectModelException: Not 
> a v4.0.0 POM.
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultM
> av
> enProjectBuilder.java:1299)
> at
> org.apache.maven.project.DefaultMavenProjectBuil

Re: Assembly problem: Error "Not a v4.0.0 POM"

2007-05-08 Thread John Casey

Okay, I've found the problem; it's in the assembly plugin, where I'm not
using the correct method to retrieve the transitive POM set (there is one
that allows "stub" models when it detects a non-4.0.0 POM, and another that
doesn't). I'm fixing it now, but it won't be released for a little while
(there are several more things that need to go into that release).

Thanks, and sorry for the inconvenience.

-john

On 5/8/07, Chris Helck <[EMAIL PROTECTED]> wrote:


I'm using maven 2.0.4. Assembly plugin is 2.2-beta-1.

I'll be happy to supply more data it needed. Stack trace is below.

Thanks,
Christopher Helck



[INFO]

[DEBUG] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to create
assembly: Error retrieving POM of module-dependency: ebs:pps:jar:3.0.2;
Reason: Not a v4.0.0 POM.
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default
LifecycleExecutor.java:559)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifec
ycle(DefaultLifecycleExecutor.java:475)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultL
ifecycleExecutor.java:454)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle
Failures(DefaultLifecycleExecutor.java:306)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
DefaultLifecycleExecutor.java:273)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec
ycleExecutor.java:140)
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.jav
a:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.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)
Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to
create assembly: Error retrieving POM of module-dependency:
ebs:pps:jar:3.0.2; Reason: Not a v4.0.0 POM.
at
org.apache.maven.plugin.assembly.mojos.AbstractAssemblyMojo.execute(Abst
ractAssemblyMojo.java:302)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMa
nager.java:412)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default
LifecycleExecutor.java:534)
... 16 more
Caused by:
org.apache.maven.plugin.assembly.archive.ArchiveCreationException: Error
retrieving POM of module-dependency: ebs:pps:jar:3.0.2; Reason: Not a
v4.0.0 POM.
at
org.apache.maven.plugin.assembly.archive.task.AddDependencySetsTask.addD
ependencySet(AddDependencySetsTask.java:114)
at
org.apache.maven.plugin.assembly.archive.task.AddDependencySetsTask.exec
ute(AddDependencySetsTask.java:90)
at
org.apache.maven.plugin.assembly.archive.phase.DependencySetAssemblyPhas
e.execute(DependencySetAssemblyPhase.java:54)
at
org.apache.maven.plugin.assembly.archive.DefaultAssemblyArchiver.createA
rchive(DefaultAssemblyArchiver.java:98)
at
org.apache.maven.plugin.assembly.mojos.AbstractAssemblyMojo.execute(Abst
ractAssemblyMojo.java:278)
... 18 more
Caused by: org.apache.maven.project.InvalidProjectModelException: Not a
v4.0.0 POM.
at
org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMav
enProjectBuilder.java:1299)
at
org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMav
enProjectBuilder.java:1270)
at
org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromReposit
ory(DefaultMavenProjectBuilder.java:471)
at
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(
DefaultMavenProjectBuilder.java:225)
at
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(
DefaultMavenProjectBuilder.java:235)
at
org.apache.maven.plugin.assembly.archive.task.AddDependencySetsTask.addD
ependencySet(AddDependencySetsTask.java:109)
... 22 more
[INFO]

[INFO] Total time: 8 seconds
[INFO] Finished at: Tue May 08 14:49:00 EDT 2007
[INFO] Final Memory: 9M/18M
[INFO]



-Original Message-
From: John Casey [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 08, 2007 12:22 PM
To: Mave

RE: Assembly problem: Error "Not a v4.0.0 POM"

2007-05-08 Thread Chris Helck
I'm using maven 2.0.4. Assembly plugin is 2.2-beta-1.

I'll be happy to supply more data it needed. Stack trace is below.

Thanks,
Christopher Helck



[INFO]

[DEBUG] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to create
assembly: Error retrieving POM of module-dependency: ebs:pps:jar:3.0.2;
Reason: Not a v4.0.0 POM.
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default
LifecycleExecutor.java:559)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifec
ycle(DefaultLifecycleExecutor.java:475)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultL
ifecycleExecutor.java:454)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle
Failures(DefaultLifecycleExecutor.java:306)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
DefaultLifecycleExecutor.java:273)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec
ycleExecutor.java:140)
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.jav
a:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.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)
Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to
create assembly: Error retrieving POM of module-dependency:
ebs:pps:jar:3.0.2; Reason: Not a v4.0.0 POM.
at
org.apache.maven.plugin.assembly.mojos.AbstractAssemblyMojo.execute(Abst
ractAssemblyMojo.java:302)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMa
nager.java:412)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default
LifecycleExecutor.java:534)
... 16 more
Caused by:
org.apache.maven.plugin.assembly.archive.ArchiveCreationException: Error
retrieving POM of module-dependency: ebs:pps:jar:3.0.2; Reason: Not a
v4.0.0 POM.
at
org.apache.maven.plugin.assembly.archive.task.AddDependencySetsTask.addD
ependencySet(AddDependencySetsTask.java:114)
at
org.apache.maven.plugin.assembly.archive.task.AddDependencySetsTask.exec
ute(AddDependencySetsTask.java:90)
at
org.apache.maven.plugin.assembly.archive.phase.DependencySetAssemblyPhas
e.execute(DependencySetAssemblyPhase.java:54)
at
org.apache.maven.plugin.assembly.archive.DefaultAssemblyArchiver.createA
rchive(DefaultAssemblyArchiver.java:98)
at
org.apache.maven.plugin.assembly.mojos.AbstractAssemblyMojo.execute(Abst
ractAssemblyMojo.java:278)
... 18 more
Caused by: org.apache.maven.project.InvalidProjectModelException: Not a
v4.0.0 POM.
at
org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMav
enProjectBuilder.java:1299)
at
org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMav
enProjectBuilder.java:1270)
at
org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromReposit
ory(DefaultMavenProjectBuilder.java:471)
at
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(
DefaultMavenProjectBuilder.java:225)
at
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(
DefaultMavenProjectBuilder.java:235)
at
org.apache.maven.plugin.assembly.archive.task.AddDependencySetsTask.addD
ependencySet(AddDependencySetsTask.java:109)
... 22 more
[INFO]

[INFO] Total time: 8 seconds
[INFO] Finished at: Tue May 08 14:49:00 EDT 2007
[INFO] Final Memory: 9M/18M
[INFO]



-Original Message-
From: John Casey [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, May 08, 2007 12:22 PM
To: Maven Users List
Subject: Re: Assembly problem: Error "Not a v4.0.0 POM"

Actually, the stacktrace for this error would be pretty valuable, just
to see whether it's coming from the assembly plugin itself, or from
maven's core...Maven's supposed to detect and ignore legacy poms.

-john

On 5/7/07, Chris Helck <[EMAIL PROTECTED]> wrote:
>
> I have an error that I don't understand.
>
> I have a maven 1 project that builds a jar file called pps-3.0.2.jar.
> The jar (a

Re: Assembly problem: Error "Not a v4.0.0 POM"

2007-05-08 Thread John Casey

Actually, the stacktrace for this error would be pretty valuable, just to
see whether it's coming from the assembly plugin itself, or from maven's
core...Maven's supposed to detect and ignore legacy poms.

-john

On 5/7/07, Chris Helck <[EMAIL PROTECTED]> wrote:


I have an error that I don't understand.

I have a maven 1 project that builds a jar file called pps-3.0.2.jar.
The jar (and it's pom) are moved into my legacy style repository.

I have a maven 2 project that depends on pps-3.0.2. It compiles and
tests the code fine. During the assembly it is suppose to creates a
directory of dependent jar files and it blows up with the message:

-
Error building POM (may not be this project's POM).

Project ID: ebs:pps
POM Location: /home/chelck/.m2/repository/ebs/pps/3.0.2/pps-3.0.2.pom

Reason: Not a v4.0.0 POM.
---
Running with -X doesn't supply any more usefull info.

In a sense the error is correct: pps-3.0.2.pom is not v4.0.0 -- it's
legacy. So why is mvn trying to build it's POM and why doesn't it
realize it's a legacy pom?

Thanks,
Christopher Helck


**
This communication and all information (including, but not limited to,
market prices/levels and data) contained therein (the "Information") is
for informational purposes only, is confidential, may be legally
privileged and is the intellectual property of ICAP plc and its affiliates
("ICAP") or third parties. No confidentiality or privilege is waived or
lost by any mistransmission. The Information is not, and should not
be construed as, an offer, bid or solicitation in relation to any
financial instrument or as an official confirmation of any transaction.
The Information is not warranted, including, but not limited, as to
completeness, timeliness or accuracy and is subject to change
without notice. ICAP assumes no liability for use or misuse of the
Information. All representations and warranties are expressly
disclaimed. The Information does not necessarily reflect the views of
ICAP. Access to the Information by anyone else other than the
recipient is unauthorized and any disclosure, copying, distribution or
any action taken or omitted to be taken in reliance on it is prohibited.
If
you receive this message in error, please immediately delete it and all
copies of it from your system, destroy any hard copies of it and
notify the sender.
**





--
John Casey
---
Maven Developer (http://maven.apache.org)
---
Blog: http://www.ejlife.net/blogs/buildchimp


Assembly problem: Error "Not a v4.0.0 POM"

2007-05-07 Thread Chris Helck
I have an error that I don't understand.

I have a maven 1 project that builds a jar file called pps-3.0.2.jar.
The jar (and it's pom) are moved into my legacy style repository. 

I have a maven 2 project that depends on pps-3.0.2. It compiles and
tests the code fine. During the assembly it is suppose to creates a
directory of dependent jar files and it blows up with the message:

-
Error building POM (may not be this project's POM).

Project ID: ebs:pps
POM Location: /home/chelck/.m2/repository/ebs/pps/3.0.2/pps-3.0.2.pom

Reason: Not a v4.0.0 POM.
---
Running with -X doesn't supply any more usefull info. 

In a sense the error is correct: pps-3.0.2.pom is not v4.0.0 -- it's
legacy. So why is mvn trying to build it's POM and why doesn't it
realize it's a legacy pom?

Thanks,
Christopher Helck


**
This communication and all information (including, but not limited to,
 market prices/levels and data) contained therein (the "Information") is
 for informational purposes only, is confidential, may be legally
 privileged and is the intellectual property of ICAP plc and its affiliates
 ("ICAP") or third parties. No confidentiality or privilege is waived or
 lost by any mistransmission. The Information is not, and should not
 be construed as, an offer, bid or solicitation in relation to any
 financial instrument or as an official confirmation of any transaction.
 The Information is not warranted, including, but not limited, as to
 completeness, timeliness or accuracy and is subject to change
 without notice. ICAP assumes no liability for use or misuse of the
 Information. All representations and warranties are expressly
 disclaimed. The Information does not necessarily reflect the views of
 ICAP. Access to the Information by anyone else other than the
 recipient is unauthorized and any disclosure, copying, distribution or
 any action taken or omitted to be taken in reliance on it is prohibited. If
 you receive this message in error, please immediately delete it and all
 copies of it from your system, destroy any hard copies of it and
 notify the sender.
**



[Maven2] [WARNING] POM for 'org.apache.axis2:axis2-kernel:pom:1.1-SNAPSHOT:compile' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM.

2006-10-31 Thread Saminda Abeyruwan

Hi,

Why am I getting the following,

[WARNING] POM for 'org.apache.axis2:axis2-kernel:pom:1.1-SNAPSHOT:compile'
is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0POM.

I'm using repositories with "legacy".

Thank you

Saminda


Continuum Gives a Not a v4.0.0 POM exception.

2006-08-29 Thread Piyush Kumar Nahata
 
Hi all,
   I'm using Continuum-1.0.3 with Maven 2.0.4. I have a multi project.
When I try to give the URL of the child project, I get the folowing
Error

--START OF STACK
TRACE

2006-08-29 09:24:38,643 [SocketListener0-9] INFO
ContinuumProjectBuilder:maven-two-builder - Downloading
http://10.225.96.127:8089/svn/repos/steam/common
2006-08-29 09:24:38,678 [SocketListener0-9] ERROR MavenBuilderHelper
- Cannot build maven project from
/work/servers/continuum-1.0.3/temp/continuum/svn/repos/steam/common (Not
a v4.0.0 POM.).

org.apache.maven.project.InvalidProjectModelException: Not a v4.0.0 POM.
at
org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMav
enProjectBuilder.java:1299)
at
org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMav
enProjectBuilder.java:1270)
at
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileI
nternal(DefaultMavenProjectBuilder.java:414)
at
org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenPr
ojectBuilder.java:201)
at
org.apache.maven.continuum.execution.maven.m2.DefaultMavenBuilderHelper.
getMavenProject(DefaultMavenBuilderHelper.java:306)
at
org.apache.maven.continuum.project.builder.maven.MavenTwoContinuumProjec
tBuilder.readModules(MavenTwoContinuumProjectBuilder.java:99)
at
org.apache.maven.continuum.project.builder.maven.MavenTwoContinuumProjec
tBuilder.buildProjectsFromMetadata(MavenTwoContinuumProjectBuilder.java:
83)
at
org.apache.maven.continuum.core.action.CreateProjectsFromMetadata.execut
e(CreateProjectsFromMetadata.java:74)
at
org.apache.maven.continuum.DefaultContinuum.executeAction(DefaultContinu
um.java:2089)
at
org.apache.maven.continuum.DefaultContinuum.executeAddProjectsFromMetada
taActivity(DefaultContinuum.java:804)
at
org.apache.maven.continuum.DefaultContinuum.addMavenTwoProject(DefaultCo
ntinuum.java:712)
at
org.apache.maven.continuum.web.action.AddMavenTwoProject.uponSuccessfulV
alidation(AddMavenTwoProject.java:52)
at
org.codehaus.plexus.formica.action.AbstractEntityAction.execute(Abstract
EntityAction.java:136)
at
org.codehaus.plexus.summit.pipeline.valve.ActionValve.invoke(ActionValve
.java:68)
at
org.codehaus.plexus.summit.pipeline.AbstractPipeline.invoke(AbstractPipe
line.java:70)
at org.codehaus.plexus.summit.Summit.doGet(Summit.java:54)
at org.codehaus.plexus.summit.Summit.doPost(Summit.java:108)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:358)
at
org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationH
andler.java:294)
at
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:567)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1807)
at
org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationCon
text.java:525)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1757)
at org.mortbay.http.HttpServer.service(HttpServer.java:879)
at
org.mortbay.http.HttpConnection.service(HttpConnection.java:789)
at
org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:960)
at
org.mortbay.http.HttpConnection.handle(HttpConnection.java:806)
at
org.mortbay.http.SocketListener.handleConnection(SocketListener.java:218
)
at
org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:331)
at
org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:520)
2006-08-29 09:24:38,680 [SocketListener0-9] INFO  Continuum
- Created 0 projects.
2006-08-29 09:24:38,680 [SocketListener0-9] INFO  Continuum
- Created 0 project groups.
2006-08-29 09:24:38,680 [SocketListener0-9] INFO  Continuum
- 1 warnings.
2006-08-29 09:24:38,681 [SocketListener0-9] INFO  Continuum
- Cannot build maven project from
/work/servers/continuum-1.0.3/temp/continuum/svn/repos/steam/common (Not
a v4.0.0 POM.).

--END OF STACK
TRACE

Here, Steam is the name of the parent project and Common is the name of
the child project that I'm trying to build.
/repos/steam/common is the structure in the Repository. 

I'm running this on Linix.

Am I missing something ?? Does anyone have any idea why, Continuum uses
temp to store the local files, when I have given a proper file path to
checkout the files.

I get this error as soon as I Give the URL and try to load the
project()i.e click on the submit button on the Continuum page). 

Any idea's are highly appreciated.

Regards,
Piyush Kumar Nahata,
 


Re: POM : Not a v4.0.0 POM / Error building POM (may not be this proj ect's POM)

2006-04-04 Thread Mang Jun Lau
hehe...first name is Mang Jun, last name is Lau.  I just go by Mang...it's 
shorter and easier :)

It's confusing because Chinese names tend to have two or three characters 
-- one for last name and the other two for first name.


_Mang Lau





"Alexandre Poitras" <[EMAIL PROTECTED]> 
04/03/2006 05:33 PM
Please respond to
"Maven Users List" 


To
"Maven Users List" 
cc

Subject
Re: POM : Not a v4.0.0 POM / Error building POM (may not be this proj 
ect's POM)






Mang Lay, you really have the eye of the tiger :)

By the way, I was wondering what was your first name and your last
name because I don't want to sound impolite ;) Asian names always
confuse me, my japanese and korean friends were always making fun of
me back in Vancouver.

On 4/3/06, Sharma, Jaikumar <[EMAIL PROTECTED]> wrote:
> Great, and Thanks Mang Jun Lau, it works. Thanks again!
> Regards.
>
> -Original Message-
> From: Mang Jun Lau [mailto:[EMAIL PROTECTED]
> Sent: Monday, April 03, 2006 7:18 PM
> To: Maven Users List
> Subject: Re: POM : Not a v4.0.0 POM / Error building POM (may not be
> this proj ect's POM)
>
>
> 4.0 needs to be
> 4.0.0 instead.
>
> Try and see if that works.
>
>
> _Mang Lau
>
>
>
>
>
> "Sharma, Jaikumar" <[EMAIL PROTECTED]>
> 04/03/2006 06:20 AM
> Please respond to
> "Maven Users List" 
>
>
> To
> Maven Users List 
> cc
>
> Subject
> POM : Not a v4.0.0 POM / Error building POM (may not be this proj ect's
> POM)
>
>
>
>
>
>
> Dear Maven users,
> When trying to execute : mvn compile I get the following error, I am not
> sure I am missing something or what is wrong . Could somebody help on
> this please ? Regards.
>
> 
> ___
>
> [INFO] Scanning for projects...
> [INFO]
> ------------
> [ERROR] FATAL ERROR
> [INFO]
> 
> [INFO] Error building POM (may not be this project's POM).
>
> Project ID: unknown
> POM Location: D:\Users\Alpha0\pom.xml
>
> Reason: Not a v4.0.0 POM.
>
> 
> ___
>
>
> http://maven.apache.org/POM/4.0.0
> <http://maven.apache.org/POM/4.0.0> "
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance
> <http://www.w3.org/2001/XMLSchema-instance> "
>   xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> <http://maven.apache.org/POM/4.0.0>
> http://maven.apache.org/maven-v4_0_0.xsd
> <http://maven.apache.org/maven-v4_0_0.xsd> ">
>
>4.0
>com.mycompany.sample
>test
>pom
>test
>4.0
>
>
>  ${basedir}
>
>
>
> 
>
> org.apache.maven.plugins.maven-archetype-plugin.1.0-alpha-3 oupI
> d>
> maven-archetype-plugin-1.0-alpha-3.jar
>   1.0-alpha-3
> 
> 
> org.apache.maven.plugins.maven-compiler-plugin.2.0
>
> maven-compiler-plugin-2.0.jar
>   2.0
> 
>
> 
> org.apache.maven.plugins.maven-install-plugin.2.1
>
> maven-install-plugin-2.1.jar
>   2.1
> 
>
> 
>org.apache.maven.plugins.maven-jar-plugin.2.0
> maven-compiler-plugin-2.0.jar
>   2.0
> 
>
> 
>
> org.apache.maven.plugins.maven-resources-plugin.2.1
> maven-resources-plugin-2.1.jar
>   2.1
> 
>
> 
>
> org.apache.maven.plugins.maven-surefire-plugin.2.1.2
> maven-compiler-plugin-2.1.2.jar
>   2.1.2
> 
>
>
>
>
>  my company
>  http://www.mycompany.com
>
>
>
>
>   ${basedir}/java/BusinessLogic/
>   ${basedir}/java/ClientUI/
>
>
>
> ${basedir}/java/BusinessLogic/src/
>
> ${basedir}/java/BusinessLogic/classes/ >
>
>   ${basedir}/java/ClientUI/
>
> ${basedir}/java/ClientUI/classes/
>
>   compile
>
>
>
>  
>
> 
> 
> 
>
>
> - - - - - - - DISCLAIMER- - - - - - - -
> Unless indicated otherwise, the information contained in this message is
> privileged and confidential, and is intended only for the use of the
> addressee(s) named above and others who have been specifically
> authorized
> to
> receive it. If you are not the intended recipient, you are hereby
> notified that any dissemination, distribution or copying of this message
> and/or attachments is strictly prohib

Re: POM : Not a v4.0.0 POM / Error building POM (may not be this proj ect's POM)

2006-04-03 Thread Alexandre Poitras
Cool thank, well I know the convention but I remember my friends use
to put it in the western order to help people to figure it out so I
always prefer to ask :)

On 4/3/06, Sharma, Jaikumar <[EMAIL PROTECTED]> wrote:
> I do not mind it. As a standard practice names are always ordered,
> , , so this is true in my case too! So, you can call my
> first name as Jaikumar :)
>
> Thanks.
>
> -Original Message-
> From: Alexandre Poitras [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, April 04, 2006 3:03 AM
> To: Maven Users List
> Subject: Re: POM : Not a v4.0.0 POM / Error building POM (may not be this
> proj ect's POM)
>
>
> Mang Lay, you really have the eye of the tiger :)
>
> By the way, I was wondering what was your first name and your last name
> because I don't want to sound impolite ;) Asian names always confuse me, my
> japanese and korean friends were always making fun of me back in Vancouver.
>
> On 4/3/06, Sharma, Jaikumar <[EMAIL PROTECTED]> wrote:
> > Great, and Thanks Mang Jun Lau, it works. Thanks again! Regards.
> >
> > -Original Message-
> > From: Mang Jun Lau [mailto:[EMAIL PROTECTED]
> > Sent: Monday, April 03, 2006 7:18 PM
> > To: Maven Users List
> > Subject: Re: POM : Not a v4.0.0 POM / Error building POM (may not be
> > this proj ect's POM)
> >
> >
> > 4.0 needs to be
> > 4.0.0 instead.
> >
> > Try and see if that works.
> >
> >
> > _Mang Lau
> >
> >
> >
> >
> >
> > "Sharma, Jaikumar" <[EMAIL PROTECTED]>
> > 04/03/2006 06:20 AM
> > Please respond to
> > "Maven Users List" 
> >
> >
> > To
> > Maven Users List 
> > cc
> >
> > Subject
> > POM : Not a v4.0.0 POM / Error building POM (may not be this proj
> > ect's
> > POM)
> >
> >
> >
> >
> >
> >
> > Dear Maven users,
> > When trying to execute : mvn compile I get the following error, I am
> > not sure I am missing something or what is wrong . Could somebody help
> > on this please ? Regards.
> >
> > __
> > __
> > ___
> >
> > [INFO] Scanning for projects...
> > [INFO]
> > --
> > --
> > [ERROR] FATAL ERROR
> > [INFO]
> > 
> > [INFO] Error building POM (may not be this project's POM).
> >
> > Project ID: unknown
> > POM Location: D:\Users\Alpha0\pom.xml
> >
> > Reason: Not a v4.0.0 POM.
> >
> > __
> > __
> > ___
> >
> >
> > http://maven.apache.org/POM/4.0.0
> > <http://maven.apache.org/POM/4.0.0> "
> > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance
> > <http://www.w3.org/2001/XMLSchema-instance> "
> >   xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> > <http://maven.apache.org/POM/4.0.0>
> > http://maven.apache.org/maven-v4_0_0.xsd
> > <http://maven.apache.org/maven-v4_0_0.xsd> ">
> >
> >4.0
> >com.mycompany.sample
> >test
> >pom
> >test
> >4.0
> >
> >
> >  ${basedir}
> >
> >
> >
> > 
> >
> > org.apache.maven.plugins.maven-archetype-plugin.1.0-alpha-3 > gr
> > oupI
> > d>
> > maven-archetype-plugin-1.0-alpha-3.jar
> >   1.0-alpha-3
> > 
> > 
> > org.apache.maven.plugins.maven-compiler-plugin.2.0
> >
> > maven-compiler-plugin-2.0.jar
> >   2.0
> > 
> >
> > 
> > org.apache.maven.plugins.maven-install-plugin.2.1
> >
> > maven-install-plugin-2.1.jar
> >   2.1
> > 
> >
> > 
> >org.apache.maven.plugins.maven-jar-plugin.2.0
> > maven-compiler-plugin-2.0.jar
> >   2.0
> > 
> >
> > 
> >
> > org.apache.maven.plugins.maven-resources-plugin.2.1
> > maven-resources-plugin-2.1.jar
> >   2.1
> > 
> >
> > 
> >
> > org.apache.maven.plugins.maven-surefire-plugin.2.1.2
> > maven-compiler-plugin-2.1.2.jar
> >   2.1.2
> > 
> >
> >
> >
> >
> >  my company
> >  http://www.mycompany.com
> >
> >
> &

RE: POM : Not a v4.0.0 POM / Error building POM (may not be this proj ect's POM)

2006-04-03 Thread Sharma, Jaikumar
I do not mind it. As a standard practice names are always ordered,
, , so this is true in my case too! So, you can call my
first name as Jaikumar :)

Thanks.

-Original Message-
From: Alexandre Poitras [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, April 04, 2006 3:03 AM
To: Maven Users List
Subject: Re: POM : Not a v4.0.0 POM / Error building POM (may not be this
proj ect's POM)


Mang Lay, you really have the eye of the tiger :)

By the way, I was wondering what was your first name and your last name
because I don't want to sound impolite ;) Asian names always confuse me, my
japanese and korean friends were always making fun of me back in Vancouver.

On 4/3/06, Sharma, Jaikumar <[EMAIL PROTECTED]> wrote:
> Great, and Thanks Mang Jun Lau, it works. Thanks again! Regards.
>
> -Original Message-
> From: Mang Jun Lau [mailto:[EMAIL PROTECTED]
> Sent: Monday, April 03, 2006 7:18 PM
> To: Maven Users List
> Subject: Re: POM : Not a v4.0.0 POM / Error building POM (may not be 
> this proj ect's POM)
>
>
> 4.0 needs to be 
> 4.0.0 instead.
>
> Try and see if that works.
>
>
> _Mang Lau
>
>
>
>
>
> "Sharma, Jaikumar" <[EMAIL PROTECTED]>
> 04/03/2006 06:20 AM
> Please respond to
> "Maven Users List" 
>
>
> To
> Maven Users List 
> cc
>
> Subject
> POM : Not a v4.0.0 POM / Error building POM (may not be this proj 
> ect's
> POM)
>
>
>
>
>
>
> Dear Maven users,
> When trying to execute : mvn compile I get the following error, I am 
> not sure I am missing something or what is wrong . Could somebody help 
> on this please ? Regards.
>
> __
> __
> ___
>
> [INFO] Scanning for projects...
> [INFO]
> --
> --
> [ERROR] FATAL ERROR
> [INFO]
> 
> [INFO] Error building POM (may not be this project's POM).
>
> Project ID: unknown
> POM Location: D:\Users\Alpha0\pom.xml
>
> Reason: Not a v4.0.0 POM.
>
> __
> __
> ___
>
>
> http://maven.apache.org/POM/4.0.0
> <http://maven.apache.org/POM/4.0.0> " 
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance
> <http://www.w3.org/2001/XMLSchema-instance> "
>   xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> <http://maven.apache.org/POM/4.0.0>
> http://maven.apache.org/maven-v4_0_0.xsd
> <http://maven.apache.org/maven-v4_0_0.xsd> ">
>
>4.0
>com.mycompany.sample
>test
>pom
>test
>4.0
>
>
>  ${basedir}
>
>
>
> 
>
> org.apache.maven.plugins.maven-archetype-plugin.1.0-alpha-3 gr
> oupI
> d>
> maven-archetype-plugin-1.0-alpha-3.jar
>   1.0-alpha-3
> 
>  
> org.apache.maven.plugins.maven-compiler-plugin.2.0
>
> maven-compiler-plugin-2.0.jar
>   2.0
> 
>
>  
> org.apache.maven.plugins.maven-install-plugin.2.1
>
> maven-install-plugin-2.1.jar
>   2.1
> 
>
> 
>org.apache.maven.plugins.maven-jar-plugin.2.0
> maven-compiler-plugin-2.0.jar
>   2.0
> 
>
> 
>
> org.apache.maven.plugins.maven-resources-plugin.2.1
> maven-resources-plugin-2.1.jar
>   2.1
> 
>
> 
>
> org.apache.maven.plugins.maven-surefire-plugin.2.1.2
> maven-compiler-plugin-2.1.2.jar
>   2.1.2
> 
>
>
>
>
>  my company
>  http://www.mycompany.com
>
>
>
>
>   ${basedir}/java/BusinessLogic/
>   ${basedir}/java/ClientUI/
>
>
> 
> ${basedir}/java/BusinessLogic/src/
>
> ${basedir}/java/BusinessLogic/classes/ ry
> >
>
>   ${basedir}/java/ClientUI/
>
> ${basedir}/java/ClientUI/classes/
>
>   compile
>
>
>
>  
>
> __
> __
> 
> 
>
>
> - - - - - - - DISCLAIMER- - - - - - - -
> Unless indicated otherwise, the information contained in this message 
> is privileged and confidential, and is intended only for the use of 
> the
> addressee(s) named above and others who have been specifically
> authorized
> to
> receive it. If you are not the intended recipient, you are hereby
> notified that any dissemination, distribution or copying of this message
> and/or attachments is strictly prohibited. The company accepts no
> liability for
> any
> damage cause

Re: POM : Not a v4.0.0 POM / Error building POM (may not be this proj ect's POM)

2006-04-03 Thread Alexandre Poitras
Mang Lay, you really have the eye of the tiger :)

By the way, I was wondering what was your first name and your last
name because I don't want to sound impolite ;) Asian names always
confuse me, my japanese and korean friends were always making fun of
me back in Vancouver.

On 4/3/06, Sharma, Jaikumar <[EMAIL PROTECTED]> wrote:
> Great, and Thanks Mang Jun Lau, it works. Thanks again!
> Regards.
>
> -Original Message-
> From: Mang Jun Lau [mailto:[EMAIL PROTECTED]
> Sent: Monday, April 03, 2006 7:18 PM
> To: Maven Users List
> Subject: Re: POM : Not a v4.0.0 POM / Error building POM (may not be
> this proj ect's POM)
>
>
> 4.0 needs to be
> 4.0.0 instead.
>
> Try and see if that works.
>
>
> _Mang Lau
>
>
>
>
>
> "Sharma, Jaikumar" <[EMAIL PROTECTED]>
> 04/03/2006 06:20 AM
> Please respond to
> "Maven Users List" 
>
>
> To
> Maven Users List 
> cc
>
> Subject
> POM : Not a v4.0.0 POM / Error building POM (may not be this proj ect's
> POM)
>
>
>
>
>
>
> Dear Maven users,
> When trying to execute : mvn compile I get the following error, I am not
> sure I am missing something or what is wrong . Could somebody help on
> this please ? Regards.
>
> 
> ___
>
> [INFO] Scanning for projects...
> [INFO]
> 
> [ERROR] FATAL ERROR
> [INFO]
> --------
> [INFO] Error building POM (may not be this project's POM).
>
> Project ID: unknown
> POM Location: D:\Users\Alpha0\pom.xml
>
> Reason: Not a v4.0.0 POM.
>
> 
> ___
>
>
> http://maven.apache.org/POM/4.0.0
> <http://maven.apache.org/POM/4.0.0> "
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance
> <http://www.w3.org/2001/XMLSchema-instance> "
>   xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> <http://maven.apache.org/POM/4.0.0>
> http://maven.apache.org/maven-v4_0_0.xsd
> <http://maven.apache.org/maven-v4_0_0.xsd> ">
>
>4.0
>com.mycompany.sample
>test
>pom
>test
>4.0
>
>
>  ${basedir}
>
>
>
> 
>
> org.apache.maven.plugins.maven-archetype-plugin.1.0-alpha-3 oupI
> d>
> maven-archetype-plugin-1.0-alpha-3.jar
>   1.0-alpha-3
> 
> 
> org.apache.maven.plugins.maven-compiler-plugin.2.0
>
> maven-compiler-plugin-2.0.jar
>   2.0
> 
>
> 
> org.apache.maven.plugins.maven-install-plugin.2.1
>
> maven-install-plugin-2.1.jar
>   2.1
> 
>
> 
>org.apache.maven.plugins.maven-jar-plugin.2.0
> maven-compiler-plugin-2.0.jar
>   2.0
> 
>
> 
>
> org.apache.maven.plugins.maven-resources-plugin.2.1
> maven-resources-plugin-2.1.jar
>   2.1
> 
>
> 
>
> org.apache.maven.plugins.maven-surefire-plugin.2.1.2
> maven-compiler-plugin-2.1.2.jar
>   2.1.2
> 
>
>
>
>
>  my company
>  http://www.mycompany.com
>
>
>
>
>   ${basedir}/java/BusinessLogic/
>   ${basedir}/java/ClientUI/
>
>
>
> ${basedir}/java/BusinessLogic/src/
>
> ${basedir}/java/BusinessLogic/classes/ >
>
>   ${basedir}/java/ClientUI/
>
> ${basedir}/java/ClientUI/classes/
>
>   compile
>
>
>
>  
>
> 
> 
> 
>
>
> - - - - - - - DISCLAIMER- - - - - - - -
> Unless indicated otherwise, the information contained in this message is
> privileged and confidential, and is intended only for the use of the
> addressee(s) named above and others who have been specifically
> authorized
> to
> receive it. If you are not the intended recipient, you are hereby
> notified that any dissemination, distribution or copying of this message
> and/or attachments is strictly prohibited. The company accepts no
> liability for
> any
> damage caused by any virus transmitted by this email. Furthermore, the
> company does not warrant a proper and complete transmission of this
> information, nor does it accept liability for any delays. If you have
> received this message in error, please contact the sender and delete the
> message. Thank you.
>
> - - - - - - - DISCLAIMER- - - - - - - -
> Unless indicated otherwise, the information contained in this message is
> privile

RE: POM : Not a v4.0.0 POM / Error building POM (may not be this proj ect's POM)

2006-04-03 Thread Sharma, Jaikumar
Great, and Thanks Mang Jun Lau, it works. Thanks again!
Regards.

-Original Message-
From: Mang Jun Lau [mailto:[EMAIL PROTECTED] 
Sent: Monday, April 03, 2006 7:18 PM
To: Maven Users List
Subject: Re: POM : Not a v4.0.0 POM / Error building POM (may not be
this proj ect's POM)


4.0 needs to be 
4.0.0 instead.

Try and see if that works.


_Mang Lau





"Sharma, Jaikumar" <[EMAIL PROTECTED]> 
04/03/2006 06:20 AM
Please respond to
"Maven Users List" 


To
Maven Users List 
cc

Subject
POM : Not a v4.0.0 POM / Error building POM (may not be this proj ect's 
POM)






Dear Maven users,
When trying to execute : mvn compile I get the following error, I am not
sure I am missing something or what is wrong . Could somebody help on
this please ? Regards.
 

___
 
[INFO] Scanning for projects...
[INFO]

[ERROR] FATAL ERROR
[INFO]

[INFO] Error building POM (may not be this project's POM).

Project ID: unknown
POM Location: D:\Users\Alpha0\pom.xml
 
Reason: Not a v4.0.0 POM.
 

___
 
 
http://maven.apache.org/POM/4.0.0
<http://maven.apache.org/POM/4.0.0> "
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance
<http://www.w3.org/2001/XMLSchema-instance> "
  xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
<http://maven.apache.org/POM/4.0.0>
http://maven.apache.org/maven-v4_0_0.xsd
<http://maven.apache.org/maven-v4_0_0.xsd> ">
 
   4.0
   com.mycompany.sample
   test
   pom
   test 
   4.0 
 
   
 ${basedir}
   
 
   

 
org.apache.maven.plugins.maven-archetype-plugin.1.0-alpha-3 
maven-archetype-plugin-1.0-alpha-3.jar
  1.0-alpha-3


org.apache.maven.plugins.maven-compiler-plugin.2.0

maven-compiler-plugin-2.0.jar
  2.0

 

org.apache.maven.plugins.maven-install-plugin.2.1

maven-install-plugin-2.1.jar
  2.1

 

   org.apache.maven.plugins.maven-jar-plugin.2.0 
maven-compiler-plugin-2.0.jar
  2.0

 

 
org.apache.maven.plugins.maven-resources-plugin.2.1 
maven-resources-plugin-2.1.jar
  2.1

 

 
org.apache.maven.plugins.maven-surefire-plugin.2.1.2 
maven-compiler-plugin-2.1.2.jar
  2.1.2

 

 
   
 my company
 http://www.mycompany.com
   
 
 
   
  ${basedir}/java/BusinessLogic/
  ${basedir}/java/ClientUI/

 
   
${basedir}/java/BusinessLogic/src/
 
${basedir}/java/BusinessLogic/classes/
 
  ${basedir}/java/ClientUI/
 
${basedir}/java/ClientUI/classes/
 
  compile
 
   
 
  
 



 
 
- - - - - - - DISCLAIMER- - - - - - - -
Unless indicated otherwise, the information contained in this message is
privileged and confidential, and is intended only for the use of the
addressee(s) named above and others who have been specifically
authorized 
to
receive it. If you are not the intended recipient, you are hereby
notified that any dissemination, distribution or copying of this message
and/or attachments is strictly prohibited. The company accepts no
liability for 
any
damage caused by any virus transmitted by this email. Furthermore, the
company does not warrant a proper and complete transmission of this
information, nor does it accept liability for any delays. If you have
received this message in error, please contact the sender and delete the
message. Thank you.

- - - - - - - DISCLAIMER- - - - - - - -
Unless indicated otherwise, the information contained in this message is
privileged and confidential, and is intended only for the use of the
addressee(s) named above and others who have been specifically authorized to
receive it. If you are not the intended recipient, you are hereby notified
that any dissemination, distribution or copying of this message and/or
attachments is strictly prohibited. The company accepts no liability for any
damage caused by any virus transmitted by this email. Furthermore, the
company does not warrant a proper and complete transmission of this
information, nor does it accept liablility for any delays. If you have
received this message in error, please contact the sender and delete the
message. Thank you.


Re: POM : Not a v4.0.0 POM / Error building POM (may not be this proj ect's POM)

2006-04-03 Thread Mang Jun Lau
4.0 needs to be 
4.0.0 instead.

Try and see if that works.


_Mang Lau





"Sharma, Jaikumar" <[EMAIL PROTECTED]> 
04/03/2006 06:20 AM
Please respond to
"Maven Users List" 


To
Maven Users List 
cc

Subject
POM : Not a v4.0.0 POM / Error building POM (may not be this proj ect's 
POM)






Dear Maven users,
When trying to execute : mvn compile I get the following error, I am not
sure I am missing something or what is wrong . Could somebody help on this
please ?
Regards.
 
___
 
[INFO] Scanning for projects...
[INFO]

[ERROR] FATAL ERROR
[INFO]

[INFO] Error building POM (may not be this project's POM).

Project ID: unknown
POM Location: D:\Users\Alpha0\pom.xml
 
Reason: Not a v4.0.0 POM.
 
___
 
 
http://maven.apache.org/POM/4.0.0
<http://maven.apache.org/POM/4.0.0> "
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance
<http://www.w3.org/2001/XMLSchema-instance> "
  xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
<http://maven.apache.org/POM/4.0.0>
http://maven.apache.org/maven-v4_0_0.xsd
<http://maven.apache.org/maven-v4_0_0.xsd> ">
 
   4.0
   com.mycompany.sample
   test
   pom
   test 
   4.0 
 
   
 ${basedir}
   
 
   

 
org.apache.maven.plugins.maven-archetype-plugin.1.0-alpha-3 
maven-archetype-plugin-1.0-alpha-3.jar
  1.0-alpha-3


 org.apache.maven.plugins.maven-compiler-plugin.2.0

maven-compiler-plugin-2.0.jar
  2.0

 

 org.apache.maven.plugins.maven-install-plugin.2.1

maven-install-plugin-2.1.jar
  2.1

 

   org.apache.maven.plugins.maven-jar-plugin.2.0 
maven-compiler-plugin-2.0.jar
  2.0

 

 
org.apache.maven.plugins.maven-resources-plugin.2.1 
maven-resources-plugin-2.1.jar
  2.1

 

 
org.apache.maven.plugins.maven-surefire-plugin.2.1.2 
maven-compiler-plugin-2.1.2.jar
  2.1.2

 

 
   
 my company
 http://www.mycompany.com
   
 
 
   
  ${basedir}/java/BusinessLogic/
  ${basedir}/java/ClientUI/

 
   
 ${basedir}/java/BusinessLogic/src/
 
${basedir}/java/BusinessLogic/classes/
 
  ${basedir}/java/ClientUI/
  ${basedir}/java/ClientUI/classes/
 
  compile
 
   
 
  
 


 
 
- - - - - - - DISCLAIMER- - - - - - - -
Unless indicated otherwise, the information contained in this message is
privileged and confidential, and is intended only for the use of the
addressee(s) named above and others who have been specifically authorized 
to
receive it. If you are not the intended recipient, you are hereby notified
that any dissemination, distribution or copying of this message and/or
attachments is strictly prohibited. The company accepts no liability for 
any
damage caused by any virus transmitted by this email. Furthermore, the
company does not warrant a proper and complete transmission of this
information, nor does it accept liability for any delays. If you have
received this message in error, please contact the sender and delete the
message. Thank you.



RE: POM : Not a v4.0.0 POM / Error building POM (may not be this proj ect's POM)

2006-04-03 Thread Sharma, Jaikumar
Alexandre, I have validated this POM with XMLSpy (a validator) against the
provided http://maven.apache.org/maven-v4_0_0.xsd . But still the same
error.
Any idea ?
Regards,

-Original Message-
From: Alexandre Poitras [mailto:[EMAIL PROTECTED] 
Sent: Monday, April 03, 2006 4:57 PM
To: Maven Users List
Subject: Re: POM : Not a v4.0.0 POM / Error building POM (may not be this
proj ect's POM)


By the way, your namespaces declaration on the project element looks weird
but maybe it is just because of  a strange copy/paste behaviour.

On 4/3/06, Alexandre Poitras <[EMAIL PROTECTED]> wrote:
> IE validate XML syntax, but don't validate its content using the DTD. 
> Open it in something like Eclipse WTP XML editor or any another XML 
> editor, it will save you a lot of time.
>
> On 4/3/06, Allison, Bob <[EMAIL PROTECTED]> wrote:
> > IE doesn't VALIDATE to XML, just display it.
> >
> > -Original Message-
> > From: Sharma, Jaikumar [mailto:[EMAIL PROTECTED]
> > Sent: Monday, April 03, 2006 07:00
> > To: Maven Users List
> > Subject: RE: POM : Not a v4.0.0 POM / Error building POM (may not be 
> > this proj ect's POM)
> >
> >
> > After copying the plugins section inside the  section, same 
> > error is there, even IE is able to parse this XML file correctly, 
> > does not show any problems. Any Idea ?
> >
> > Regards.
> >
> > -Original Message-----
> > From: Alexandre Poitras [mailto:[EMAIL PROTECTED]
> > Sent: Monday, April 03, 2006 4:14 PM
> > To: Maven Users List
> > Subject: Re: POM : Not a v4.0.0 POM / Error building POM (may not be 
> > this proj ect's POM)
> >
> >
> > Your plugins section is not inside the build section. An XML aware 
> > editor could help you there :)
> >
> > On 4/3/06, Sharma, Jaikumar <[EMAIL PROTECTED]> wrote:
> > > Dear Maven users,
> > > When trying to execute : mvn compile I get the following error, I 
> > > am not sure I am missing something or what is wrong . Could 
> > > somebody help on this please ? Regards.
> > >
> > > __
> > > 
> > > _
> > >
> > > [INFO] Scanning for projects...
> > > [INFO]
> > > --------------
> > > 
> > > --
> > > [ERROR] FATAL ERROR
> > > [INFO]
> > >

> > > [INFO] Error building POM (may not be this project's POM).
> > >
> > > Project ID: unknown
> > > POM Location: D:\Users\Alpha0\pom.xml
> > >
> > > Reason: Not a v4.0.0 POM.
> > >
> > > __
> > > 
> > > _
> > >
> > >
> > > http://maven.apache.org/POM/4.0.0
> > > <http://maven.apache.org/POM/4.0.0> " 
> > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance
> > > <http://www.w3.org/2001/XMLSchema-instance> "
> > >   xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> > > <http://maven.apache.org/POM/4.0.0>
> > > http://maven.apache.org/maven-v4_0_0.xsd
> > > <http://maven.apache.org/maven-v4_0_0.xsd> ">
> > >
> > >4.0
> > >com.mycompany.sample
> > >test
> > >pom
> > >test
> > >4.0
> > >
> > >  ${basedir}
> > >
> > >
> > >
> > > 
> > >
> > > org.apache.maven.plugins.maven-archetype-plugin.1.0-alpha
> > > -3 > > groupI
> > > d>
> > > maven-archetype-plugin-1.0-alpha-3.jar
> > >   1.0-alpha-3
> > > 
> > > 
> > >
> > > org.apache.maven.plugins.maven-compiler-plugin.2.0 > > Id>
> > >
> > > maven-compiler-plugin-2.0.jar
> > >   2.0
> > > 
> > >
> > > 
> > >
> > > org.apache.maven.plugins.maven-install-plugin.2.1 > > d>
> > >
> > > maven-install-plugin-2.1.jar
> > >   2.1
> > > 
> > >
> > > 
> > >
org.apache.maven.plugins.maven-jar-plugin.2.0
> > > maven-compiler-plugin-2.0.jar
> > >   2.0
> > > 
> > >
> > > 
> > >
> > > org.apache.maven.plugins.maven-resources-plugin.2.1
> > >

RE: POM : Not a v4.0.0 POM / Error building POM (may not be this proj ect's POM)

2006-04-03 Thread Sharma, Jaikumar
Yes. Alexandre, this is because of copy / paste behaviour only :)

-Original Message-
From: Alexandre Poitras [mailto:[EMAIL PROTECTED] 
Sent: Monday, April 03, 2006 4:57 PM
To: Maven Users List
Subject: Re: POM : Not a v4.0.0 POM / Error building POM (may not be this
proj ect's POM)


By the way, your namespaces declaration on the project element looks weird
but maybe it is just because of  a strange copy/paste behaviour.

On 4/3/06, Alexandre Poitras <[EMAIL PROTECTED]> wrote:
> IE validate XML syntax, but don't validate its content using the DTD. 
> Open it in something like Eclipse WTP XML editor or any another XML 
> editor, it will save you a lot of time.
>
> On 4/3/06, Allison, Bob <[EMAIL PROTECTED]> wrote:
> > IE doesn't VALIDATE to XML, just display it.
> >
> > -Original Message-
> > From: Sharma, Jaikumar [mailto:[EMAIL PROTECTED]
> > Sent: Monday, April 03, 2006 07:00
> > To: Maven Users List
> > Subject: RE: POM : Not a v4.0.0 POM / Error building POM (may not be 
> > this proj ect's POM)
> >
> >
> > After copying the plugins section inside the  section, same 
> > error is there, even IE is able to parse this XML file correctly, 
> > does not show any problems. Any Idea ?
> >
> > Regards.
> >
> > -Original Message-----
> > From: Alexandre Poitras [mailto:[EMAIL PROTECTED]
> > Sent: Monday, April 03, 2006 4:14 PM
> > To: Maven Users List
> > Subject: Re: POM : Not a v4.0.0 POM / Error building POM (may not be 
> > this proj ect's POM)
> >
> >
> > Your plugins section is not inside the build section. An XML aware 
> > editor could help you there :)
> >
> > On 4/3/06, Sharma, Jaikumar <[EMAIL PROTECTED]> wrote:
> > > Dear Maven users,
> > > When trying to execute : mvn compile I get the following error, I 
> > > am not sure I am missing something or what is wrong . Could 
> > > somebody help on this please ? Regards.
> > >
> > > __
> > > 
> > > _
> > >
> > > [INFO] Scanning for projects...
> > > [INFO]
> > > --------------
> > > 
> > > --
> > > [ERROR] FATAL ERROR
> > > [INFO]
> > >

> > > [INFO] Error building POM (may not be this project's POM).
> > >
> > > Project ID: unknown
> > > POM Location: D:\Users\Alpha0\pom.xml
> > >
> > > Reason: Not a v4.0.0 POM.
> > >
> > > __
> > > 
> > > _
> > >
> > >
> > > http://maven.apache.org/POM/4.0.0
> > > <http://maven.apache.org/POM/4.0.0> " 
> > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance
> > > <http://www.w3.org/2001/XMLSchema-instance> "
> > >   xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> > > <http://maven.apache.org/POM/4.0.0>
> > > http://maven.apache.org/maven-v4_0_0.xsd
> > > <http://maven.apache.org/maven-v4_0_0.xsd> ">
> > >
> > >4.0
> > >com.mycompany.sample
> > >test
> > >pom
> > >test
> > >4.0
> > >
> > >  ${basedir}
> > >
> > >
> > >
> > > 
> > >
> > > org.apache.maven.plugins.maven-archetype-plugin.1.0-alpha
> > > -3 > > groupI
> > > d>
> > > maven-archetype-plugin-1.0-alpha-3.jar
> > >   1.0-alpha-3
> > > 
> > > 
> > >
> > > org.apache.maven.plugins.maven-compiler-plugin.2.0 > > Id>
> > >
> > > maven-compiler-plugin-2.0.jar
> > >   2.0
> > > 
> > >
> > > 
> > >
> > > org.apache.maven.plugins.maven-install-plugin.2.1 > > d>
> > >
> > > maven-install-plugin-2.1.jar
> > >   2.1
> > > 
> > >
> > > 
> > >
org.apache.maven.plugins.maven-jar-plugin.2.0
> > > maven-compiler-plugin-2.0.jar
> > >   2.0
> > > 
> > >
> > > 
> > >
> > > org.apache.maven.plugins.maven-resources-plugin.2.1
> > > maven-resources-plugin-2.1.jar
> > >   2.1
> > > 
> > >
> > >

RE: POM : Not a v4.0.0 POM / Error building POM (may not be this proj ect's POM)

2006-04-03 Thread Sharma, Jaikumar
Yes Alexandre, I also believe so. Thanks. As I tried to remove the one
closing tag, and IE came with an Error.

-Original Message-
From: Alexandre Poitras [mailto:[EMAIL PROTECTED] 
Sent: Monday, April 03, 2006 4:55 PM
To: Maven Users List
Subject: Re: POM : Not a v4.0.0 POM / Error building POM (may not be this
proj ect's POM)


IE validate XML syntax, but don't validate its content using the DTD. Open
it in something like Eclipse WTP XML editor or any another XML editor, it
will save you a lot of time.

On 4/3/06, Allison, Bob <[EMAIL PROTECTED]> wrote:
> IE doesn't VALIDATE to XML, just display it.
>
> -Original Message-
> From: Sharma, Jaikumar [mailto:[EMAIL PROTECTED]
> Sent: Monday, April 03, 2006 07:00
> To: Maven Users List
> Subject: RE: POM : Not a v4.0.0 POM / Error building POM (may not be 
> this proj ect's POM)
>
>
> After copying the plugins section inside the  section, same 
> error is there, even IE is able to parse this XML file correctly, does 
> not show any problems. Any Idea ?
>
> Regards.
>
> -Original Message-
> From: Alexandre Poitras [mailto:[EMAIL PROTECTED]
> Sent: Monday, April 03, 2006 4:14 PM
> To: Maven Users List
> Subject: Re: POM : Not a v4.0.0 POM / Error building POM (may not be 
> this proj ect's POM)
>
>
> Your plugins section is not inside the build section. An XML aware 
> editor could help you there :)
>
> On 4/3/06, Sharma, Jaikumar <[EMAIL PROTECTED]> wrote:
> > Dear Maven users,
> > When trying to execute : mvn compile I get the following error, I am 
> > not sure I am missing something or what is wrong . Could somebody 
> > help on this please ? Regards.
> >
> > 
> > __
> > _
> >
> > [INFO] Scanning for projects...
> > [INFO]
> > 
> > --
> > --
> > [ERROR] FATAL ERROR
> > [INFO]
> > ------------
> > [INFO] Error building POM (may not be this project's POM).
> >
> > Project ID: unknown
> > POM Location: D:\Users\Alpha0\pom.xml
> >
> > Reason: Not a v4.0.0 POM.
> >
> > 
> > __
> > _
> >
> >
> > http://maven.apache.org/POM/4.0.0
> > <http://maven.apache.org/POM/4.0.0> " 
> > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance
> > <http://www.w3.org/2001/XMLSchema-instance> "
> >   xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> > <http://maven.apache.org/POM/4.0.0>
> > http://maven.apache.org/maven-v4_0_0.xsd
> > <http://maven.apache.org/maven-v4_0_0.xsd> ">
> >
> >4.0
> >com.mycompany.sample
> >test
> >pom
> >test
> >4.0
> >
> >
> >  ${basedir}
> >
> >
> >
> > 
> >
> > org.apache.maven.plugins.maven-archetype-plugin.1.0-alpha-3
> >  > groupI
> > d>
> > maven-archetype-plugin-1.0-alpha-3.jar
> >   1.0-alpha-3
> > 
> > 
> >
> > org.apache.maven.plugins.maven-compiler-plugin.2.0 > >
> >
> > maven-compiler-plugin-2.0.jar
> >   2.0
> > 
> >
> > 
> >
> > org.apache.maven.plugins.maven-install-plugin.2.1
> >
> > maven-install-plugin-2.1.jar
> >   2.1
> > 
> >
> > 
> >org.apache.maven.plugins.maven-jar-plugin.2.0
> > maven-compiler-plugin-2.0.jar
> >   2.0
> > 
> >
> > 
> >
> > org.apache.maven.plugins.maven-resources-plugin.2.1
> > maven-resources-plugin-2.1.jar
> >   2.1
> > 
> >
> > 
> >
> > org.apache.maven.plugins.maven-surefire-plugin.2.1.2
> > maven-compiler-plugin-2.1.2.jar
> >   2.1.2
> > 
> >
> >
> >
> >
> >  my company
> >  http://www.mycompany.com
> >
> >
> >
> >
> >   ${basedir}/java/BusinessLogic/
> >   ${basedir}/java/ClientUI/
> >
> >
> >
> >
> > ${basedir}/java/BusinessLogic/src/ > >
> >
> > ${basedir}/java/BusinessLogic/classes/ > to
> > ry>
> >
> >   ${basedir}/java/ClientUI/
> >
> > ${basedir}/java/ClientUI/classes/
> >
> >   compile
> >
> >
>

Re: POM : Not a v4.0.0 POM / Error building POM (may not be this proj ect's POM)

2006-04-03 Thread Alexandre Poitras
By the way, your namespaces declaration on the project element looks
weird but maybe it is just because of  a strange copy/paste behaviour.

On 4/3/06, Alexandre Poitras <[EMAIL PROTECTED]> wrote:
> IE validate XML syntax, but don't validate its content using the DTD.
> Open it in something like Eclipse WTP XML editor or any another XML
> editor, it will save you a lot of time.
>
> On 4/3/06, Allison, Bob <[EMAIL PROTECTED]> wrote:
> > IE doesn't VALIDATE to XML, just display it.
> >
> > -Original Message-
> > From: Sharma, Jaikumar [mailto:[EMAIL PROTECTED]
> > Sent: Monday, April 03, 2006 07:00
> > To: Maven Users List
> > Subject: RE: POM : Not a v4.0.0 POM / Error building POM (may not be this 
> > proj ect's POM)
> >
> >
> > After copying the plugins section inside the  section, same error is
> > there, even IE is able to parse this XML file correctly, does not show any
> > problems.
> > Any Idea ?
> >
> > Regards.
> >
> > -Original Message-----
> > From: Alexandre Poitras [mailto:[EMAIL PROTECTED]
> > Sent: Monday, April 03, 2006 4:14 PM
> > To: Maven Users List
> > Subject: Re: POM : Not a v4.0.0 POM / Error building POM (may not be this
> > proj ect's POM)
> >
> >
> > Your plugins section is not inside the build section. An XML aware editor
> > could help you there :)
> >
> > On 4/3/06, Sharma, Jaikumar <[EMAIL PROTECTED]> wrote:
> > > Dear Maven users,
> > > When trying to execute : mvn compile I get the following error, I am
> > > not sure I am missing something or what is wrong . Could somebody help
> > > on this please ? Regards.
> > >
> > > __
> > > _
> > >
> > > [INFO] Scanning for projects...
> > > [INFO]
> > > --------------
> > > --
> > > [ERROR] FATAL ERROR
> > > [INFO]
> > > 
> > > [INFO] Error building POM (may not be this project's POM).
> > >
> > > Project ID: unknown
> > > POM Location: D:\Users\Alpha0\pom.xml
> > >
> > > Reason: Not a v4.0.0 POM.
> > >
> > > __
> > > _
> > >
> > >
> > > http://maven.apache.org/POM/4.0.0
> > > <http://maven.apache.org/POM/4.0.0> "
> > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance
> > > <http://www.w3.org/2001/XMLSchema-instance> "
> > >   xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> > > <http://maven.apache.org/POM/4.0.0>
> > > http://maven.apache.org/maven-v4_0_0.xsd
> > > <http://maven.apache.org/maven-v4_0_0.xsd> ">
> > >
> > >4.0
> > >com.mycompany.sample
> > >test
> > >pom
> > >test
> > >4.0
> > >
> > >
> > >  ${basedir}
> > >
> > >
> > >
> > > 
> > >
> > > org.apache.maven.plugins.maven-archetype-plugin.1.0-alpha-3 > > groupI
> > > d>
> > > maven-archetype-plugin-1.0-alpha-3.jar
> > >   1.0-alpha-3
> > > 
> > > 
> > >
> > > org.apache.maven.plugins.maven-compiler-plugin.2.0
> > >
> > > maven-compiler-plugin-2.0.jar
> > >   2.0
> > > 
> > >
> > > 
> > >
> > > org.apache.maven.plugins.maven-install-plugin.2.1
> > >
> > > maven-install-plugin-2.1.jar
> > >   2.1
> > > 
> > >
> > > 
> > >org.apache.maven.plugins.maven-jar-plugin.2.0
> > > maven-compiler-plugin-2.0.jar
> > >   2.0
> > > 
> > >
> > > 
> > >
> > > org.apache.maven.plugins.maven-resources-plugin.2.1
> > > maven-resources-plugin-2.1.jar
> > >   2.1
> > > 
> > >
> > > 
> > >
> > > org.apache.maven.plugins.maven-surefire-plugin.2.1.2
> > > maven-compiler-plugin-2.1.2.jar
> > >   2.1.2
> > > 
> > >
> > >
> > >
> > >
> > >  my company
> > >  http://www.mycompany.com
> > >
> > >
> > &

RE: POM : Not a v4.0.0 POM / Error building POM (may not be this proj ect's POM)

2006-04-03 Thread Sharma, Jaikumar
Thanks Allison, I would validate it first.

-Original Message-
From: Allison, Bob [mailto:[EMAIL PROTECTED] 
Sent: Monday, April 03, 2006 4:35 PM
To: Maven Users List
Subject: RE: POM : Not a v4.0.0 POM / Error building POM (may not be this
proj ect's POM)


IE doesn't VALIDATE to XML, just display it.

-Original Message-
From: Sharma, Jaikumar [mailto:[EMAIL PROTECTED] 
Sent: Monday, April 03, 2006 07:00
To: Maven Users List
Subject: RE: POM : Not a v4.0.0 POM / Error building POM (may not be this
proj ect's POM)


After copying the plugins section inside the  section, same error is
there, even IE is able to parse this XML file correctly, does not show any
problems. Any Idea ?

Regards. 

-Original Message-
From: Alexandre Poitras [mailto:[EMAIL PROTECTED] 
Sent: Monday, April 03, 2006 4:14 PM
To: Maven Users List
Subject: Re: POM : Not a v4.0.0 POM / Error building POM (may not be this
proj ect's POM)


Your plugins section is not inside the build section. An XML aware editor
could help you there :)

On 4/3/06, Sharma, Jaikumar <[EMAIL PROTECTED]> wrote:
> Dear Maven users,
> When trying to execute : mvn compile I get the following error, I am
> not sure I am missing something or what is wrong . Could somebody help 
> on this please ? Regards.
>
> __
> _
>
> [INFO] Scanning for projects...
> [INFO]
> --
> --
> [ERROR] FATAL ERROR
> [INFO]
> --
> --
> [INFO] Error building POM (may not be this project's POM).
>
> Project ID: unknown
> POM Location: D:\Users\Alpha0\pom.xml
>
> Reason: Not a v4.0.0 POM.
>
> __
> _
>
>
> http://maven.apache.org/POM/4.0.0
> <http://maven.apache.org/POM/4.0.0> "
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance
> <http://www.w3.org/2001/XMLSchema-instance> "
>   xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> <http://maven.apache.org/POM/4.0.0>
> http://maven.apache.org/maven-v4_0_0.xsd
> <http://maven.apache.org/maven-v4_0_0.xsd> ">
>
>4.0
>com.mycompany.sample
>test
>pom
>test
>4.0
>
>
>  ${basedir}
>
>
>
> 
>
> org.apache.maven.plugins.maven-archetype-plugin.1.0-alpha-3 groupI
> d>
> maven-archetype-plugin-1.0-alpha-3.jar
>   1.0-alpha-3
> 
> 
>
> org.apache.maven.plugins.maven-compiler-plugin.2.0
>
> maven-compiler-plugin-2.0.jar
>   2.0
> 
>
> 
>
> org.apache.maven.plugins.maven-install-plugin.2.1
>
> maven-install-plugin-2.1.jar
>   2.1
> 
>
> 
>org.apache.maven.plugins.maven-jar-plugin.2.0
> maven-compiler-plugin-2.0.jar
>   2.0
> 
>
> 
>
> org.apache.maven.plugins.maven-resources-plugin.2.1
> maven-resources-plugin-2.1.jar
>   2.1
> 
>
> 
>
> org.apache.maven.plugins.maven-surefire-plugin.2.1.2
> maven-compiler-plugin-2.1.2.jar
>   2.1.2
> 
>
>
>
>
>  my company
>  http://www.mycompany.com
>
>
>
>
>   ${basedir}/java/BusinessLogic/
>   ${basedir}/java/ClientUI/
>
>
>
>   
> ${basedir}/java/BusinessLogic/src/
>
> ${basedir}/java/BusinessLogic/classes/ ry>
>
>   ${basedir}/java/ClientUI/
>   
> ${basedir}/java/ClientUI/classes/
>
>   compile
>
>
>
>  
>
> __
> __
> 
>
>
> - - - - - - - DISCLAIMER- - - - - - - -
> Unless indicated otherwise, the information contained in this message
> is privileged and confidential, and is intended only for the use of 
> the
> addressee(s) named above and others who have been specifically authorized
to
> receive it. If you are not the intended recipient, you are hereby 
> notified that any dissemination, distribution or copying of this 
> message and/or attachments is strictly prohibited. The company accepts 
> no liability for
any
> damage caused by any virus transmitted by this email. Furthermore, the 
> company does not warrant a proper and complete transmission of this 
> information, nor does it accept liability for any delays. If you have 
> received this message in error, please contact the sender and delete 
> the message. Thank you.
>
>


--
Alexandre Poitras
Québec, Canada

-

Re: POM : Not a v4.0.0 POM / Error building POM (may not be this proj ect's POM)

2006-04-03 Thread Alexandre Poitras
IE validate XML syntax, but don't validate its content using the DTD.
Open it in something like Eclipse WTP XML editor or any another XML
editor, it will save you a lot of time.

On 4/3/06, Allison, Bob <[EMAIL PROTECTED]> wrote:
> IE doesn't VALIDATE to XML, just display it.
>
> -Original Message-
> From: Sharma, Jaikumar [mailto:[EMAIL PROTECTED]
> Sent: Monday, April 03, 2006 07:00
> To: Maven Users List
> Subject: RE: POM : Not a v4.0.0 POM / Error building POM (may not be this 
> proj ect's POM)
>
>
> After copying the plugins section inside the  section, same error is
> there, even IE is able to parse this XML file correctly, does not show any
> problems.
> Any Idea ?
>
> Regards.
>
> -Original Message-
> From: Alexandre Poitras [mailto:[EMAIL PROTECTED]
> Sent: Monday, April 03, 2006 4:14 PM
> To: Maven Users List
> Subject: Re: POM : Not a v4.0.0 POM / Error building POM (may not be this
> proj ect's POM)
>
>
> Your plugins section is not inside the build section. An XML aware editor
> could help you there :)
>
> On 4/3/06, Sharma, Jaikumar <[EMAIL PROTECTED]> wrote:
> > Dear Maven users,
> > When trying to execute : mvn compile I get the following error, I am
> > not sure I am missing something or what is wrong . Could somebody help
> > on this please ? Regards.
> >
> > __
> > _
> >
> > [INFO] Scanning for projects...
> > [INFO]
> > --
> > --
> > [ERROR] FATAL ERROR
> > [INFO]
> > ----------------
> > [INFO] Error building POM (may not be this project's POM).
> >
> > Project ID: unknown
> > POM Location: D:\Users\Alpha0\pom.xml
> >
> > Reason: Not a v4.0.0 POM.
> >
> > __
> > _
> >
> >
> > http://maven.apache.org/POM/4.0.0
> > <http://maven.apache.org/POM/4.0.0> "
> > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance
> > <http://www.w3.org/2001/XMLSchema-instance> "
> >   xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> > <http://maven.apache.org/POM/4.0.0>
> > http://maven.apache.org/maven-v4_0_0.xsd
> > <http://maven.apache.org/maven-v4_0_0.xsd> ">
> >
> >4.0
> >com.mycompany.sample
> >test
> >pom
> >test
> >4.0
> >
> >
> >  ${basedir}
> >
> >
> >
> > 
> >
> > org.apache.maven.plugins.maven-archetype-plugin.1.0-alpha-3 > groupI
> > d>
> > maven-archetype-plugin-1.0-alpha-3.jar
> >   1.0-alpha-3
> > 
> > 
> >
> > org.apache.maven.plugins.maven-compiler-plugin.2.0
> >
> > maven-compiler-plugin-2.0.jar
> >   2.0
> > 
> >
> > 
> >
> > org.apache.maven.plugins.maven-install-plugin.2.1
> >
> > maven-install-plugin-2.1.jar
> >   2.1
> > 
> >
> > 
> >org.apache.maven.plugins.maven-jar-plugin.2.0
> > maven-compiler-plugin-2.0.jar
> >   2.0
> > 
> >
> > 
> >
> > org.apache.maven.plugins.maven-resources-plugin.2.1
> > maven-resources-plugin-2.1.jar
> >   2.1
> > 
> >
> > 
> >
> > org.apache.maven.plugins.maven-surefire-plugin.2.1.2
> > maven-compiler-plugin-2.1.2.jar
> >   2.1.2
> > 
> >
> >
> >
> >
> >  my company
> >  http://www.mycompany.com
> >
> >
> >
> >
> >   ${basedir}/java/BusinessLogic/
> >   ${basedir}/java/ClientUI/
> >
> >
> >
> >
> > ${basedir}/java/BusinessLogic/src/
> >
> > ${basedir}/java/BusinessLogic/classes/ > ry>
> >
> >   ${basedir}/java/ClientUI/
> >
> > ${basedir}/java/ClientUI/classes/
> >
> >   compile
> >
> >
> >
> >  
> >
> > __
> > __
> > 
> >
> >
> > - - - - - - - DISCLAIMER- - - - - - - -
> > Unless indicated otherwise, the information contained in this message
> > is privileged and confidential, and is intended only for the use of
> > the
> > addressee(s) named above and others 

RE: POM : Not a v4.0.0 POM / Error building POM (may not be this proj ect's POM)

2006-04-03 Thread Allison, Bob
IE doesn't VALIDATE to XML, just display it.

-Original Message-
From: Sharma, Jaikumar [mailto:[EMAIL PROTECTED] 
Sent: Monday, April 03, 2006 07:00
To: Maven Users List
Subject: RE: POM : Not a v4.0.0 POM / Error building POM (may not be this proj 
ect's POM)


After copying the plugins section inside the  section, same error is
there, even IE is able to parse this XML file correctly, does not show any
problems.
Any Idea ?

Regards. 

-Original Message-
From: Alexandre Poitras [mailto:[EMAIL PROTECTED] 
Sent: Monday, April 03, 2006 4:14 PM
To: Maven Users List
Subject: Re: POM : Not a v4.0.0 POM / Error building POM (may not be this
proj ect's POM)


Your plugins section is not inside the build section. An XML aware editor
could help you there :)

On 4/3/06, Sharma, Jaikumar <[EMAIL PROTECTED]> wrote:
> Dear Maven users,
> When trying to execute : mvn compile I get the following error, I am 
> not sure I am missing something or what is wrong . Could somebody help 
> on this please ? Regards.
>
> __
> _
>
> [INFO] Scanning for projects...
> [INFO]
> --
> --
> [ERROR] FATAL ERROR
> [INFO]
> 
> [INFO] Error building POM (may not be this project's POM).
>
> Project ID: unknown
> POM Location: D:\Users\Alpha0\pom.xml
>
> Reason: Not a v4.0.0 POM.
>
> __
> _
>
>
> http://maven.apache.org/POM/4.0.0
> <http://maven.apache.org/POM/4.0.0> " 
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance
> <http://www.w3.org/2001/XMLSchema-instance> "
>   xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> <http://maven.apache.org/POM/4.0.0>
> http://maven.apache.org/maven-v4_0_0.xsd
> <http://maven.apache.org/maven-v4_0_0.xsd> ">
>
>4.0
>com.mycompany.sample
>test
>pom
>test
>4.0
>
>
>  ${basedir}
>
>
>
> 
>
> org.apache.maven.plugins.maven-archetype-plugin.1.0-alpha-3 groupI
> d>
> maven-archetype-plugin-1.0-alpha-3.jar
>   1.0-alpha-3
> 
> 
>
> org.apache.maven.plugins.maven-compiler-plugin.2.0
>
> maven-compiler-plugin-2.0.jar
>   2.0
> 
>
> 
>
> org.apache.maven.plugins.maven-install-plugin.2.1
>
> maven-install-plugin-2.1.jar
>   2.1
> 
>
> 
>org.apache.maven.plugins.maven-jar-plugin.2.0
> maven-compiler-plugin-2.0.jar
>   2.0
> 
>
> 
>
> org.apache.maven.plugins.maven-resources-plugin.2.1
> maven-resources-plugin-2.1.jar
>   2.1
> 
>
> 
>
> org.apache.maven.plugins.maven-surefire-plugin.2.1.2
> maven-compiler-plugin-2.1.2.jar
>   2.1.2
> 
>
>
>
>
>  my company
>  http://www.mycompany.com
>
>
>
>
>   ${basedir}/java/BusinessLogic/
>   ${basedir}/java/ClientUI/
>
>
>
>   
> ${basedir}/java/BusinessLogic/src/
>
> ${basedir}/java/BusinessLogic/classes/ ry>
>
>   ${basedir}/java/ClientUI/
>   
> ${basedir}/java/ClientUI/classes/
>
>   compile
>
>
>
>  
>
> __
> __
> 
>
>
> - - - - - - - DISCLAIMER- - - - - - - -
> Unless indicated otherwise, the information contained in this message 
> is privileged and confidential, and is intended only for the use of 
> the
> addressee(s) named above and others who have been specifically authorized
to
> receive it. If you are not the intended recipient, you are hereby notified
> that any dissemination, distribution or copying of this message and/or
> attachments is strictly prohibited. The company accepts no liability for
any
> damage caused by any virus transmitted by this email. Furthermore, the
> company does not warrant a proper and complete transmission of this
> information, nor does it accept liability for any delays. If you have
> received this message in error, please contact the sender and delete the
> message. Thank you.
>
>


--
Alexandre Poitras
Québec, Canada

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

- - - - - - - DISCLAIMER- - - - - - - -
Unless indicated otherwise, the information contained in this message is
privileged and confidential, and is intended only for the use of

RE: POM : Not a v4.0.0 POM / Error building POM (may not be this proj ect's POM)

2006-04-03 Thread Sharma, Jaikumar
After copying the plugins section inside the  section, same error is
there, even IE is able to parse this XML file correctly, does not show any
problems.
Any Idea ?

Regards. 

-Original Message-
From: Alexandre Poitras [mailto:[EMAIL PROTECTED] 
Sent: Monday, April 03, 2006 4:14 PM
To: Maven Users List
Subject: Re: POM : Not a v4.0.0 POM / Error building POM (may not be this
proj ect's POM)


Your plugins section is not inside the build section. An XML aware editor
could help you there :)

On 4/3/06, Sharma, Jaikumar <[EMAIL PROTECTED]> wrote:
> Dear Maven users,
> When trying to execute : mvn compile I get the following error, I am 
> not sure I am missing something or what is wrong . Could somebody help 
> on this please ? Regards.
>
> __
> _
>
> [INFO] Scanning for projects...
> [INFO]
> --
> --
> [ERROR] FATAL ERROR
> [INFO]
> 
> [INFO] Error building POM (may not be this project's POM).
>
> Project ID: unknown
> POM Location: D:\Users\Alpha0\pom.xml
>
> Reason: Not a v4.0.0 POM.
>
> __
> _
>
>
> http://maven.apache.org/POM/4.0.0
> <http://maven.apache.org/POM/4.0.0> " 
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance
> <http://www.w3.org/2001/XMLSchema-instance> "
>   xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> <http://maven.apache.org/POM/4.0.0>
> http://maven.apache.org/maven-v4_0_0.xsd
> <http://maven.apache.org/maven-v4_0_0.xsd> ">
>
>4.0
>com.mycompany.sample
>test
>pom
>test
>4.0
>
>
>  ${basedir}
>
>
>
> 
>
> org.apache.maven.plugins.maven-archetype-plugin.1.0-alpha-3 groupI
> d>
> maven-archetype-plugin-1.0-alpha-3.jar
>   1.0-alpha-3
> 
> 
>
> org.apache.maven.plugins.maven-compiler-plugin.2.0
>
> maven-compiler-plugin-2.0.jar
>   2.0
> 
>
> 
>
> org.apache.maven.plugins.maven-install-plugin.2.1
>
> maven-install-plugin-2.1.jar
>   2.1
> 
>
> 
>org.apache.maven.plugins.maven-jar-plugin.2.0
> maven-compiler-plugin-2.0.jar
>   2.0
> 
>
> 
>
> org.apache.maven.plugins.maven-resources-plugin.2.1
> maven-resources-plugin-2.1.jar
>   2.1
> 
>
> 
>
> org.apache.maven.plugins.maven-surefire-plugin.2.1.2
> maven-compiler-plugin-2.1.2.jar
>   2.1.2
> 
>
>
>
>
>  my company
>  http://www.mycompany.com
>
>
>
>
>   ${basedir}/java/BusinessLogic/
>   ${basedir}/java/ClientUI/
>
>
>
>   
> ${basedir}/java/BusinessLogic/src/
>
> ${basedir}/java/BusinessLogic/classes/ ry>
>
>   ${basedir}/java/ClientUI/
>   
> ${basedir}/java/ClientUI/classes/
>
>   compile
>
>
>
>  
>
> __
> __
> 
>
>
> - - - - - - - DISCLAIMER- - - - - - - -
> Unless indicated otherwise, the information contained in this message 
> is privileged and confidential, and is intended only for the use of 
> the
> addressee(s) named above and others who have been specifically authorized
to
> receive it. If you are not the intended recipient, you are hereby notified
> that any dissemination, distribution or copying of this message and/or
> attachments is strictly prohibited. The company accepts no liability for
any
> damage caused by any virus transmitted by this email. Furthermore, the
> company does not warrant a proper and complete transmission of this
> information, nor does it accept liability for any delays. If you have
> received this message in error, please contact the sender and delete the
> message. Thank you.
>
>


--
Alexandre Poitras
Québec, Canada

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

- - - - - - - DISCLAIMER- - - - - - - -
Unless indicated otherwise, the information contained in this message is
privileged and confidential, and is intended only for the use of the
addressee(s) named above and others who have been specifically authorized to
receive it. If you are not the intended recipient, you are hereby notified
that any dissemination, distribution or copying of this message and/or
attachments is strictly prohibited. The company accepts no liability for any
damage caused by any virus transmitted by this email. Furthermore, the
company does not warrant a proper and complete transmission of this
information, nor does it accept liablility for any delays. If you have
received this message in error, please contact the sender and delete the
message. Thank you.


Re: POM : Not a v4.0.0 POM / Error building POM (may not be this proj ect's POM)

2006-04-03 Thread Alexandre Poitras
Your plugins section is not inside the build section. An XML aware
editor could help you there :)

On 4/3/06, Sharma, Jaikumar <[EMAIL PROTECTED]> wrote:
> Dear Maven users,
> When trying to execute : mvn compile I get the following error, I am not
> sure I am missing something or what is wrong . Could somebody help on this
> please ?
> Regards.
>
> ___
>
> [INFO] Scanning for projects...
> [INFO]
> 
> [ERROR] FATAL ERROR
> [INFO]
> 
> [INFO] Error building POM (may not be this project's POM).
>
> Project ID: unknown
> POM Location: D:\Users\Alpha0\pom.xml
>
> Reason: Not a v4.0.0 POM.
>
> ___
>
>
> http://maven.apache.org/POM/4.0.0
> <http://maven.apache.org/POM/4.0.0> "
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance
> <http://www.w3.org/2001/XMLSchema-instance> "
>   xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> <http://maven.apache.org/POM/4.0.0>
> http://maven.apache.org/maven-v4_0_0.xsd
> <http://maven.apache.org/maven-v4_0_0.xsd> ">
>
>4.0
>com.mycompany.sample
>test
>pom
>test
>4.0
>
>
>  ${basedir}
>
>
>
> 
>
> org.apache.maven.plugins.maven-archetype-plugin.1.0-alpha-3 d>
> maven-archetype-plugin-1.0-alpha-3.jar
>   1.0-alpha-3
> 
> 
>org.apache.maven.plugins.maven-compiler-plugin.2.0
>
> maven-compiler-plugin-2.0.jar
>   2.0
> 
>
> 
>org.apache.maven.plugins.maven-install-plugin.2.1
>
> maven-install-plugin-2.1.jar
>   2.1
> 
>
> 
>org.apache.maven.plugins.maven-jar-plugin.2.0
> maven-compiler-plugin-2.0.jar
>   2.0
> 
>
> 
>
> org.apache.maven.plugins.maven-resources-plugin.2.1
> maven-resources-plugin-2.1.jar
>   2.1
> 
>
> 
>
> org.apache.maven.plugins.maven-surefire-plugin.2.1.2
> maven-compiler-plugin-2.1.2.jar
>   2.1.2
> 
>
>
>
>
>  my company
>  http://www.mycompany.com
>
>
>
>
>   ${basedir}/java/BusinessLogic/
>   ${basedir}/java/ClientUI/
>
>
>
>   ${basedir}/java/BusinessLogic/src/
>
> ${basedir}/java/BusinessLogic/classes/
>
>   ${basedir}/java/ClientUI/
>   ${basedir}/java/ClientUI/classes/
>
>   compile
>
>
>
>  
>
> 
> 
>
>
> - - - - - - - DISCLAIMER- - - - - - - -
> Unless indicated otherwise, the information contained in this message is
> privileged and confidential, and is intended only for the use of the
> addressee(s) named above and others who have been specifically authorized to
> receive it. If you are not the intended recipient, you are hereby notified
> that any dissemination, distribution or copying of this message and/or
> attachments is strictly prohibited. The company accepts no liability for any
> damage caused by any virus transmitted by this email. Furthermore, the
> company does not warrant a proper and complete transmission of this
> information, nor does it accept liability for any delays. If you have
> received this message in error, please contact the sender and delete the
> message. Thank you.
>
>


--
Alexandre Poitras
Québec, Canada

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



POM : Not a v4.0.0 POM / Error building POM (may not be this proj ect's POM)

2006-04-03 Thread Sharma, Jaikumar
Dear Maven users,
When trying to execute : mvn compile I get the following error, I am not
sure I am missing something or what is wrong . Could somebody help on this
please ?
Regards.
 
___
 
[INFO] Scanning for projects...
[INFO]

[ERROR] FATAL ERROR
[INFO]

[INFO] Error building POM (may not be this project's POM).

Project ID: unknown
POM Location: D:\Users\Alpha0\pom.xml
 
Reason: Not a v4.0.0 POM.
 
___
 
 
http://maven.apache.org/POM/4.0.0
<http://maven.apache.org/POM/4.0.0> "
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance
<http://www.w3.org/2001/XMLSchema-instance> "
  xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
<http://maven.apache.org/POM/4.0.0>
http://maven.apache.org/maven-v4_0_0.xsd
<http://maven.apache.org/maven-v4_0_0.xsd> ">
 
   4.0
   com.mycompany.sample
   test
   pom
   test 
   4.0 
   
   
 ${basedir}
   
   
   

 
org.apache.maven.plugins.maven-archetype-plugin.1.0-alpha-3  
maven-archetype-plugin-1.0-alpha-3.jar
  1.0-alpha-3


   org.apache.maven.plugins.maven-compiler-plugin.2.0

maven-compiler-plugin-2.0.jar
  2.0



   org.apache.maven.plugins.maven-install-plugin.2.1

maven-install-plugin-2.1.jar
  2.1

 

   org.apache.maven.plugins.maven-jar-plugin.2.0  
maven-compiler-plugin-2.0.jar
  2.0



 
org.apache.maven.plugins.maven-resources-plugin.2.1  
maven-resources-plugin-2.1.jar
  2.1



 
org.apache.maven.plugins.maven-surefire-plugin.2.1.2  
maven-compiler-plugin-2.1.2.jar
  2.1.2

 
 
 
   
 my company
 http://www.mycompany.com
   
   
   
   
  ${basedir}/java/BusinessLogic/
  ${basedir}/java/ClientUI/
  
 
   
  ${basedir}/java/BusinessLogic/src/
 
${basedir}/java/BusinessLogic/classes/
 
  ${basedir}/java/ClientUI/
  ${basedir}/java/ClientUI/classes/
 
  compile
  
   
   
  
 


 
 
- - - - - - - DISCLAIMER- - - - - - - -
Unless indicated otherwise, the information contained in this message is
privileged and confidential, and is intended only for the use of the
addressee(s) named above and others who have been specifically authorized to
receive it. If you are not the intended recipient, you are hereby notified
that any dissemination, distribution or copying of this message and/or
attachments is strictly prohibited. The company accepts no liability for any
damage caused by any virus transmitted by this email. Furthermore, the
company does not warrant a proper and complete transmission of this
information, nor does it accept liability for any delays. If you have
received this message in error, please contact the sender and delete the
message. Thank you.