Re: Now seriously: how can I manage dependencies of own projects with maven

2010-10-18 Thread Stephen Connolly
On 18 October 2010 23:15, Zac Thompson  wrote:
> On Fri, Oct 15, 2010 at 6:34 AM, Stephen Connolly
>  wrote:
>> I just set up a big fat aggrigator for each of the "test everything
>> together" projects that I want to run CI over. I use svn:externals to
>> check everything out and then two maven builders, first to update the
>> aggregator and all child modules to link them together and the second
>> to run "verify".  That way I never pollute the local repo... and these
>> types of build run less frequently (hourly), so the slower build is
>> less of an issue.
>>
>
> Thanks for this bit, Stephen; I've been considering doing exactly this
> for a little while, so it's good to know you've already proven it can
> work well in practice.  I think nightly is good enough in my case.  I
> haven't tried using externals with Hudson yet, so I'm curious: does
> your hourly build always run whether there have been changes or not,
> or are you getting Hudson to check for updates first?

I set it as downstream of each module's job so that if the
svn:externals build correctly, then we trigger a build of the latest
integration uber-build

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

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



Re: Maven SQL plugin

2010-10-18 Thread Chris Odney
Folks,

Can I specify wildcards like "c:\SQLscripts\create\*.sql" for the 
attribute within ?


We have our db scripts in separate folders like create, upgrade,
constraints, triggers etc.

As the name says create folders has sql files that have db script to create
tables, upgrade has scripts to alter the tables incase we add/remove any
columns etc, constraints folder has sql scripts to add foreign key, indexes
etc.

Sql files within a particular folder can be executed in any order, it does
not matter. However, the folders must be picked up in a predefined order,
eg: create, upgrade, constraints triggers etc.

In this case, I cannot use the  as the ordering mechanism is
alphabetical.  seems a good choice however I cannot specify
wildcards :(

Any help?

Thanks,
Chris.



On Fri, Oct 15, 2010 at 3:48 AM, John Singleton wrote:

> http://jira.codehaus.org/browse/MSQL-53
>
> addresses exactly this issue...
>
> On Thu, Oct 14, 2010 at 5:12 PM, John Singleton  >wrote:
>
> > Hi Chris,
> >
> > It has been my experience of ~2.5 years that the order is maintained with
> a
> >  list, though I see nothing in the plugin docs that specifically
> > mentions this, nor have I had the time (or inclination) to read the
> > source...  We have a relatively small number of sql files, 4 in one
> place, 2
> > in another, so it is not too bad for us to list them all by name.  FWIW,
> we
> > are using version 1.4 of the plugin.
> >
> > Cheers,
> > John
> >
> >
> > On Thu, Oct 14, 2010 at 10:27 AM, Chris Odney  >wrote:
> >
> >> Hi John,
> >>
> >> I never noticed the option of  as against 
> >>
> >> My understanding is the list of files specified using  are
> >> executed in the order they are specified whereas it is not so in the
> case
> >> of
> >> (this is when orderFile attribute is not specified). Am I
> wrong?
> >>
> >> Thanks for the reply,
> >> Chris.
> >>
> >> On Thu, Oct 14, 2010 at 7:33 PM, John Singleton  >> >wrote:
> >>
> >> > Hi Chris,
> >> >
> >> > #2 is probably the best to ensure repeatability in the order you want.
> >>  It
> >> > also prevents inadvertent re-ordering if a new sql file is introduced
> >> into
> >> > the sql directory.  In our project, we use srcFiles rather than
> fileset:
> >> >
> >> > 
> >> >[file1]
> >> >[file2}
> >> >...
> >> > 
> >> >
> >> > HTH,
> >> > John Singleton
> >> >
> >> > On Thu, Oct 14, 2010 at 9:25 AM, Chris Odney 
> >> > wrote:
> >> >
> >> > > Hi,
> >> > >
> >> > > I am facing some problem in ordering the sql execution.
> >> > >
> >> > > We have one sql script file for each table under one directory. Ex:
> >> There
> >> > > is
> >> > > user.sql and role.sql in the directory c:\SqlScripts. We are using
> the
> >> > sql
> >> > > maven plugin to execute these sql files.
> >> > >
> >> > > The role table has a Foriegn key to the user table and the execution
> >> is
> >> > > failing because the plugin is trying to execute the role.sql before
> >> > > user.sql. I cannot use the  orderfile attribute as we specify the
> >> > 
> >> > > as c:\SqlScripts\*.sql.
> >> > >
> >> > > How do I overcome this problem?
> >> > >
> >> > > I see 2 solutions:
> >> > >
> >> > > 1) Merge all scripts into one file in the creation order, the script
> >> to
> >> > > create role comes after the script to create user.
> >> > >
> >> > > 2)Remove the * wildcard and specify each file in the 
> >> attribute
> >> > > in
> >> > > the order of execution.
> >> > >
> >> > > 3)Number the name of the files according to the execution order ex:
> >> > > 1_user.sql, 2_role.sql and use the 'ascending' orderfile
> attribute(not
> >> > sure
> >> > > if this would work though, as the ordering may not be applied)
> >> > >
> >> > > Any more elegant solutions?
> >> > >
> >> > > Thank you,
> >> > > Chris.
> >> > >
> >> >
> >>
> >
> >
>


Re: clean then package error

2010-10-18 Thread Anders Hammar
You're doing tis from Eclipse/m2eclipe, right? Not command line? Is you're
Eclipseset up to use a JDK?
http://tech.karolzielinski.com/m2eclipse-eclipse-is-running-in-a-jre-but-a-jdk-is-required

/Anders

2010/10/19 冯仁君 

> yes,I know. but I have set the JAVA_HOME pointing to the directory of JDK.
> and when I run package without clean before, it works well.
> if I run clean, and then package, it's error!
>
> --
> From: "MK Tan" 
> Sent: Monday, October 18, 2010 11:34 PM
> To: "Maven Users List" 
> Subject: Re: clean then package error
>
>  I should spell check before I sending this mail.
>>
>> Maven need jdk and not jre.
>> And if possible please include environment variable called JAVA_HOME which
>> point to your jdk installation directory
>>
>> 2010/10/18 MK Tan 
>>
>>  Haven require jdk but you are refer to jre
>>>
>>> On Oct 18, 2010 8:46 PM, "冯仁君"  wrote:
>>> > I'm new in using maven. when I try to package a helloworld maven >
>>> program
>>> after I clean in the Eclipse IDE, it comes to an error. it says :
>>> >
>>> > [ERROR] Failed to execute goal
>>> org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile
>>> (default-compile) on project module: Compilation failure
>>> > Unable to locate the Javac Compiler in:
>>> > D:\Java\jre6\..\lib\tools.jar
>>> > Please ensure you are using JDK 1.4 or above and
>>> > not a JRE (the com.sun.tools.javac.Main class is required).
>>> > In most cases you can change the location of your Java
>>> > installation by setting the JAVA_HOME environment variable.
>>> > -> [Help 1]
>>> > [ERROR]
>>> > [ERROR] To see the full stack trace of the errors, re-run Maven with >
>>> the
>>> -e switch.
>>> > [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>>> > [ERROR]
>>> > [ERROR] For more information about the errors and possible solutions,
>>> please read the following articles:
>>> > [ERROR] [Help 1]
>>> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
>>> > [ERROR]
>>> > [ERROR] After correcting the problems, you can resume the build with >
>>> the
>>> command
>>> > [ERROR] mvn  -rf :module
>>> >
>>> > I'm sure I have installed the jdk1.6, and my environment variable is >
>>> also
>>> correct. I don't it's the problem of maven, but I don't know what to do.
>>> what can I do?
>>>
>>>
>>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>


Re: clean then package error

2010-10-18 Thread 冯仁君

yes,I know. but I have set the JAVA_HOME pointing to the directory of JDK.
and when I run package without clean before, it works well.
if I run clean, and then package, it's error!

--
From: "MK Tan" 
Sent: Monday, October 18, 2010 11:34 PM
To: "Maven Users List" 
Subject: Re: clean then package error


I should spell check before I sending this mail.

Maven need jdk and not jre.
And if possible please include environment variable called JAVA_HOME which
point to your jdk installation directory

2010/10/18 MK Tan 


Haven require jdk but you are refer to jre

On Oct 18, 2010 8:46 PM, "冯仁君"  wrote:
> I'm new in using maven. when I try to package a helloworld maven 
> program

after I clean in the Eclipse IDE, it comes to an error. it says :
>
> [ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile
(default-compile) on project module: Compilation failure
> Unable to locate the Javac Compiler in:
> D:\Java\jre6\..\lib\tools.jar
> Please ensure you are using JDK 1.4 or above and
> not a JRE (the com.sun.tools.javac.Main class is required).
> In most cases you can change the location of your Java
> installation by setting the JAVA_HOME environment variable.
> -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with 
> the

-e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions,
please read the following articles:
> [ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with 
> the

command
> [ERROR] mvn  -rf :module
>
> I'm sure I have installed the jdk1.6, and my environment variable is 
> also

correct. I don't it's the problem of maven, but I don't know what to do.
what can I do?






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



Re: Compiler encoding on SuSE Linux

2010-10-18 Thread Wayne Fay
> I'm not so good at Linux internals. Is there another variable or setting
> that I could check?

mvn -X package (or compile, or another phase) might tell you more info
about what Maven (and its various plugins) are doing.

Wayne

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



Re: Now seriously: how can I manage dependencies of own projects with maven

2010-10-18 Thread Zac Thompson
On Fri, Oct 15, 2010 at 6:34 AM, Stephen Connolly
 wrote:
> I just set up a big fat aggrigator for each of the "test everything
> together" projects that I want to run CI over. I use svn:externals to
> check everything out and then two maven builders, first to update the
> aggregator and all child modules to link them together and the second
> to run "verify".  That way I never pollute the local repo... and these
> types of build run less frequently (hourly), so the slower build is
> less of an issue.
>

Thanks for this bit, Stephen; I've been considering doing exactly this
for a little while, so it's good to know you've already proven it can
work well in practice.  I think nightly is good enough in my case.  I
haven't tried using externals with Hudson yet, so I'm curious: does
your hourly build always run whether there have been changes or not,
or are you getting Hudson to check for updates first?

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



Re: Compiler encoding on SuSE Linux

2010-10-18 Thread Andreas Simon
I thought that Maven simply compiles the source file to a class file, so 
it's one chance for re-encoding.


I'm not so good at Linux internals. Is there another variable or setting 
that I could check?

If you encode/decode one too many times you could get some weird
behavior, like Ü(default)->  Ü(utf8) ->  Ü(utf8)(utf8) and this one
could be unreadable.

Does both shell/java read that variable? As I remember those
parameters, $LANG, could be used differently on different
linus-dists...

Cheers,
Per

On Mon, Oct 18, 2010 at 11:39 PM, Andreas Simon  wrote:
   

The application is not internationalized, so I don't use property files in
the test code or tested code.

The $LANG variable is de_DE.utf8 on both machines.

Sorry, I didn't catch your last point.

Am 18.10.2010 23:30, per-henrik hedman wrote:
 

Are you using property files in resources? Those could be stored
differently.

What are your default encoding on your machines? It could be that some
of the behavior, eg the different configurations that you are using
aren't used and then it falls back to default behavior.

Another thing can be that your are encoding an extra time, and that
could make that kind of weird behavior...

Good luck,
Per


On Mon, Oct 18, 2010 at 11:11 PM, Andreas Simon
  wrote:

   

I verified the source code and the test code file with Linux' file
command.
Both are identified as "UTF-8 Unicode Java program text". I checked on
the
failing SuSE system.

Am 18.10.2010 22:54, Anders Hammar wrote:

 

Have you verified that all Java files involved are in fact using UTF-8
char
encoding (check on the machine where it fails!)? Check both source code
and
test code files.
I don't think it's obvious that the are compiled with different
encodings.
The problem could maybe be that they are retrieved from your scm (or
stored
in the scm) with the wrong encoding.

/Anders

On Mon, Oct 18, 2010 at 22:30, Andreas Simon
  wrote:



   

Thank you for your reply!

On my developer machine is Ubuntu 10.04. Same result when running
Oracle
JDK 1.6.0u21.

  What are you running on your developer machine? Can you run it with
Oracle


 

JDK?

Cheers,
Per Hedman

On Mon, Oct 18, 2010 at 8:51 PM, Andreas Simon
  wrote:




   

Hi all,

I got a quite strange problem with my tests. I have 3 tests that
shall
control some messages for the user. These messages contain some
German
umlauts (ä, ö, ü and ß). On my Ubuntu developer machine the tests run
fine.
On my SuSE integration server the tests fail. The assertions fail
with
the
following message:

   expected:<...ü...>   but was:<...??...>

Obviously, the test files and the tested file are compiled with
different
encodings.

I have tried several settings with UTF-8,




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


src-compile
compile

compile


1.5
1.5
UTF-8
true
UTF-8
UTF-8
-Dfile.encoding=utf8



default-compile
test-compile

testCompile


1.5
1.5
UTF-8
true
UTF-8
UTF-8
-Dfile.encoding=utf8




1.5
1.5
UTF-8
true
UTF-8
UTF-8
-Dfile.encoding=utf8






UTF-8
UTF-8


Some settings are redundant, but two are better than one. Any way,
these
settings don't apply to the compiling of the test files. I have
searched
some hours for similar problems, but I found no other solution. To be
complete, my configuration:

  SuSE 11.1
  IBM JDK 1.5.0
  Maven 2.2.1


Thanks for any idea,
Andreas





 

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






   

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




 


   

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



 

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



   


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


 

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


   



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



Re: Compiler encoding on SuSE Linux

2010-10-18 Thread per-henrik hedman
If you encode/decode one too many times you could get some weird
behavior, like Ü(default)-> Ü(utf8) -> Ü(utf8)(utf8) and this one
could be unreadable.

Does both shell/java read that variable? As I remember those
parameters, $LANG, could be used differently on different
linus-dists...

Cheers,
Per

On Mon, Oct 18, 2010 at 11:39 PM, Andreas Simon  wrote:
> The application is not internationalized, so I don't use property files in
> the test code or tested code.
>
> The $LANG variable is de_DE.utf8 on both machines.
>
> Sorry, I didn't catch your last point.
>
> Am 18.10.2010 23:30, per-henrik hedman wrote:
>>
>> Are you using property files in resources? Those could be stored
>> differently.
>>
>> What are your default encoding on your machines? It could be that some
>> of the behavior, eg the different configurations that you are using
>> aren't used and then it falls back to default behavior.
>>
>> Another thing can be that your are encoding an extra time, and that
>> could make that kind of weird behavior...
>>
>> Good luck,
>> Per
>>
>>
>> On Mon, Oct 18, 2010 at 11:11 PM, Andreas Simon
>>  wrote:
>>
>>>
>>> I verified the source code and the test code file with Linux' file
>>> command.
>>> Both are identified as "UTF-8 Unicode Java program text". I checked on
>>> the
>>> failing SuSE system.
>>>
>>> Am 18.10.2010 22:54, Anders Hammar wrote:
>>>

 Have you verified that all Java files involved are in fact using UTF-8
 char
 encoding (check on the machine where it fails!)? Check both source code
 and
 test code files.
 I don't think it's obvious that the are compiled with different
 encodings.
 The problem could maybe be that they are retrieved from your scm (or
 stored
 in the scm) with the wrong encoding.

 /Anders

 On Mon, Oct 18, 2010 at 22:30, Andreas Simon
  wrote:



>
> Thank you for your reply!
>
> On my developer machine is Ubuntu 10.04. Same result when running
> Oracle
> JDK 1.6.0u21.
>
>  What are you running on your developer machine? Can you run it with
> Oracle
>
>
>>
>> JDK?
>>
>> Cheers,
>> Per Hedman
>>
>> On Mon, Oct 18, 2010 at 8:51 PM, Andreas Simon
>>  wrote:
>>
>>
>>
>>
>>>
>>> Hi all,
>>>
>>> I got a quite strange problem with my tests. I have 3 tests that
>>> shall
>>> control some messages for the user. These messages contain some
>>> German
>>> umlauts (ä, ö, ü and ß). On my Ubuntu developer machine the tests run
>>> fine.
>>> On my SuSE integration server the tests fail. The assertions fail
>>> with
>>> the
>>> following message:
>>>
>>>   expected:<...ü...>     but was:<...??...>
>>>
>>> Obviously, the test files and the tested file are compiled with
>>> different
>>> encodings.
>>>
>>> I have tried several settings with UTF-8,
>>>
>>> 
>>> 
>>> 
>>> org.apache.maven.plugins
>>> maven-compiler-plugin
>>> 2.3.2
>>> 
>>> 
>>> src-compile
>>> compile
>>> 
>>> compile
>>> 
>>> 
>>> 1.5
>>> 1.5
>>> UTF-8
>>> true
>>> UTF-8
>>> UTF-8
>>> -Dfile.encoding=utf8
>>> 
>>> 
>>> 
>>> default-compile
>>> test-compile
>>> 
>>> testCompile
>>> 
>>> 
>>> 1.5
>>> 1.5
>>> UTF-8
>>> true
>>> UTF-8
>>> UTF-8
>>> -Dfile.encoding=utf8
>>> 
>>> 
>>> 
>>> 
>>> 1.5
>>> 1.5
>>> UTF-8
>>> true
>>> UTF-8
>>> UTF-8
>>> -Dfile.encoding=utf8
>>> 
>>> 
>>> 
>>> 
>>>
>>> 
>>> UTF-8
>>> UTF-8
>>> 
>>>
>>> Some settings are redundant, but two are better than one. Any way,
>>> these
>>> settings don't apply to the compiling of the test files. I have
>>> searched
>>> some hours for similar problems, but I found no other solution. To be
>>> complete, my configuration:
>>>
>>>  SuSE 11.1
>>>  IBM JDK 1.5.0
>>>  Maven 2.2.1
>>>
>>>
>>> Thanks for any idea,
>>> Andreas
>>>
>>>
>>>
>>>
>>>
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> For additional commands, e-mail: users-h...@maven.apache.org
>>
>>
>>
>>
>>
>>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>
>
>


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

Re: Compiler encoding on SuSE Linux

2010-10-18 Thread Andreas Simon
The application is not internationalized, so I don't use property files 
in the test code or tested code.


The $LANG variable is de_DE.utf8 on both machines.

Sorry, I didn't catch your last point.

Am 18.10.2010 23:30, per-henrik hedman wrote:

Are you using property files in resources? Those could be stored differently.

What are your default encoding on your machines? It could be that some
of the behavior, eg the different configurations that you are using
aren't used and then it falls back to default behavior.

Another thing can be that your are encoding an extra time, and that
could make that kind of weird behavior...

Good luck,
Per


On Mon, Oct 18, 2010 at 11:11 PM, Andreas Simon  wrote:
   

I verified the source code and the test code file with Linux' file command.
Both are identified as "UTF-8 Unicode Java program text". I checked on the
failing SuSE system.

Am 18.10.2010 22:54, Anders Hammar wrote:
 

Have you verified that all Java files involved are in fact using UTF-8
char
encoding (check on the machine where it fails!)? Check both source code
and
test code files.
I don't think it's obvious that the are compiled with different encodings.
The problem could maybe be that they are retrieved from your scm (or
stored
in the scm) with the wrong encoding.

/Anders

On Mon, Oct 18, 2010 at 22:30, Andreas Simonwrote:


   

Thank you for your reply!

On my developer machine is Ubuntu 10.04. Same result when running Oracle
JDK 1.6.0u21.

  What are you running on your developer machine? Can you run it with
Oracle

 

JDK?

Cheers,
Per Hedman

On Mon, Oct 18, 2010 at 8:51 PM, Andreas Simon
  wrote:



   

Hi all,

I got a quite strange problem with my tests. I have 3 tests that shall
control some messages for the user. These messages contain some German
umlauts (ä, ö, ü and ß). On my Ubuntu developer machine the tests run
fine.
On my SuSE integration server the tests fail. The assertions fail with
the
following message:

   expected:<...ü...> but was:<...??...>

Obviously, the test files and the tested file are compiled with
different
encodings.

I have tried several settings with UTF-8,




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


src-compile
compile

compile


1.5
1.5
UTF-8
true
UTF-8
UTF-8
-Dfile.encoding=utf8



default-compile
test-compile

testCompile


1.5
1.5
UTF-8
true
UTF-8
UTF-8
-Dfile.encoding=utf8




1.5
1.5
UTF-8
true
UTF-8
UTF-8
-Dfile.encoding=utf8






UTF-8
UTF-8


Some settings are redundant, but two are better than one. Any way,
these
settings don't apply to the compiling of the test files. I have
searched
some hours for similar problems, but I found no other solution. To be
complete, my configuration:

  SuSE 11.1
  IBM JDK 1.5.0
  Maven 2.2.1


Thanks for any idea,
Andreas




 

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





   

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



 


   


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


 

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


   



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



Re: Compiler encoding on SuSE Linux

2010-10-18 Thread per-henrik hedman
Are you using property files in resources? Those could be stored differently.

What are your default encoding on your machines? It could be that some
of the behavior, eg the different configurations that you are using
aren't used and then it falls back to default behavior.

Another thing can be that your are encoding an extra time, and that
could make that kind of weird behavior...

Good luck,
Per


On Mon, Oct 18, 2010 at 11:11 PM, Andreas Simon  wrote:
> I verified the source code and the test code file with Linux' file command.
> Both are identified as "UTF-8 Unicode Java program text". I checked on the
> failing SuSE system.
>
> Am 18.10.2010 22:54, Anders Hammar wrote:
>>
>> Have you verified that all Java files involved are in fact using UTF-8
>> char
>> encoding (check on the machine where it fails!)? Check both source code
>> and
>> test code files.
>> I don't think it's obvious that the are compiled with different encodings.
>> The problem could maybe be that they are retrieved from your scm (or
>> stored
>> in the scm) with the wrong encoding.
>>
>> /Anders
>>
>> On Mon, Oct 18, 2010 at 22:30, Andreas Simon  wrote:
>>
>>
>>>
>>> Thank you for your reply!
>>>
>>> On my developer machine is Ubuntu 10.04. Same result when running Oracle
>>> JDK 1.6.0u21.
>>>
>>>  What are you running on your developer machine? Can you run it with
>>> Oracle
>>>

 JDK?

 Cheers,
 Per Hedman

 On Mon, Oct 18, 2010 at 8:51 PM, Andreas Simon
  wrote:



>
> Hi all,
>
> I got a quite strange problem with my tests. I have 3 tests that shall
> control some messages for the user. These messages contain some German
> umlauts (ä, ö, ü and ß). On my Ubuntu developer machine the tests run
> fine.
> On my SuSE integration server the tests fail. The assertions fail with
> the
> following message:
>
>   expected:<...ü...>   but was:<...??...>
>
> Obviously, the test files and the tested file are compiled with
> different
> encodings.
>
> I have tried several settings with UTF-8,
>
> 
> 
> 
> org.apache.maven.plugins
> maven-compiler-plugin
> 2.3.2
> 
> 
> src-compile
> compile
> 
> compile
> 
> 
> 1.5
> 1.5
> UTF-8
> true
> UTF-8
> UTF-8
> -Dfile.encoding=utf8
> 
> 
> 
> default-compile
> test-compile
> 
> testCompile
> 
> 
> 1.5
> 1.5
> UTF-8
> true
> UTF-8
> UTF-8
> -Dfile.encoding=utf8
> 
> 
> 
> 
> 1.5
> 1.5
> UTF-8
> true
> UTF-8
> UTF-8
> -Dfile.encoding=utf8
> 
> 
> 
> 
>
> 
> UTF-8
> UTF-8
> 
>
> Some settings are redundant, but two are better than one. Any way,
> these
> settings don't apply to the compiling of the test files. I have
> searched
> some hours for similar problems, but I found no other solution. To be
> complete, my configuration:
>
>  SuSE 11.1
>  IBM JDK 1.5.0
>  Maven 2.2.1
>
>
> Thanks for any idea,
> Andreas
>
>
>
>

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





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

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



Re: Compiler encoding on SuSE Linux

2010-10-18 Thread Andreas Simon
I verified the source code and the test code file with Linux' file 
command. Both are identified as "UTF-8 Unicode Java program text". I 
checked on the failing SuSE system.


Am 18.10.2010 22:54, Anders Hammar wrote:

Have you verified that all Java files involved are in fact using UTF-8 char
encoding (check on the machine where it fails!)? Check both source code and
test code files.
I don't think it's obvious that the are compiled with different encodings.
The problem could maybe be that they are retrieved from your scm (or stored
in the scm) with the wrong encoding.

/Anders

On Mon, Oct 18, 2010 at 22:30, Andreas Simon  wrote:

   

Thank you for your reply!

On my developer machine is Ubuntu 10.04. Same result when running Oracle
JDK 1.6.0u21.

  What are you running on your developer machine? Can you run it with Oracle
 

JDK?

Cheers,
Per Hedman

On Mon, Oct 18, 2010 at 8:51 PM, Andreas Simon
  wrote:


   

Hi all,

I got a quite strange problem with my tests. I have 3 tests that shall
control some messages for the user. These messages contain some German
umlauts (ä, ö, ü and ß). On my Ubuntu developer machine the tests run
fine.
On my SuSE integration server the tests fail. The assertions fail with
the
following message:

   expected:<...ü...>   but was:<...??...>

Obviously, the test files and the tested file are compiled with different
encodings.

I have tried several settings with UTF-8,




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


src-compile
compile

compile


1.5
1.5
UTF-8
true
UTF-8
UTF-8
-Dfile.encoding=utf8



default-compile
test-compile

testCompile


1.5
1.5
UTF-8
true
UTF-8
UTF-8
-Dfile.encoding=utf8




1.5
1.5
UTF-8
true
UTF-8
UTF-8
-Dfile.encoding=utf8






UTF-8
UTF-8


Some settings are redundant, but two are better than one. Any way, these
settings don't apply to the compiling of the test files. I have searched
some hours for similar problems, but I found no other solution. To be
complete, my configuration:

  SuSE 11.1
  IBM JDK 1.5.0
  Maven 2.2.1


Thanks for any idea,
Andreas



 

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




   


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


 
   



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



Re: Compiler encoding on SuSE Linux

2010-10-18 Thread Anders Hammar
Have you verified that all Java files involved are in fact using UTF-8 char
encoding (check on the machine where it fails!)? Check both source code and
test code files.
I don't think it's obvious that the are compiled with different encodings.
The problem could maybe be that they are retrieved from your scm (or stored
in the scm) with the wrong encoding.

/Anders

On Mon, Oct 18, 2010 at 22:30, Andreas Simon  wrote:

> Thank you for your reply!
>
> On my developer machine is Ubuntu 10.04. Same result when running Oracle
> JDK 1.6.0u21.
>
>  What are you running on your developer machine? Can you run it with Oracle
>> JDK?
>>
>> Cheers,
>> Per Hedman
>>
>> On Mon, Oct 18, 2010 at 8:51 PM, Andreas Simon
>>  wrote:
>>
>>
>>> Hi all,
>>>
>>> I got a quite strange problem with my tests. I have 3 tests that shall
>>> control some messages for the user. These messages contain some German
>>> umlauts (ä, ö, ü and ß). On my Ubuntu developer machine the tests run
>>> fine.
>>> On my SuSE integration server the tests fail. The assertions fail with
>>> the
>>> following message:
>>>
>>>   expected:<...ü...>  but was:<...??...>
>>>
>>> Obviously, the test files and the tested file are compiled with different
>>> encodings.
>>>
>>> I have tried several settings with UTF-8,
>>>
>>> 
>>> 
>>> 
>>> org.apache.maven.plugins
>>> maven-compiler-plugin
>>> 2.3.2
>>> 
>>> 
>>> src-compile
>>> compile
>>> 
>>> compile
>>> 
>>> 
>>> 1.5
>>> 1.5
>>> UTF-8
>>> true
>>> UTF-8
>>> UTF-8
>>> -Dfile.encoding=utf8
>>> 
>>> 
>>> 
>>> default-compile
>>> test-compile
>>> 
>>> testCompile
>>> 
>>> 
>>> 1.5
>>> 1.5
>>> UTF-8
>>> true
>>> UTF-8
>>> UTF-8
>>> -Dfile.encoding=utf8
>>> 
>>> 
>>> 
>>> 
>>> 1.5
>>> 1.5
>>> UTF-8
>>> true
>>> UTF-8
>>> UTF-8
>>> -Dfile.encoding=utf8
>>> 
>>> 
>>> 
>>> 
>>>
>>> 
>>> UTF-8
>>> UTF-8
>>> 
>>>
>>> Some settings are redundant, but two are better than one. Any way, these
>>> settings don't apply to the compiling of the test files. I have searched
>>> some hours for similar problems, but I found no other solution. To be
>>> complete, my configuration:
>>>
>>>  SuSE 11.1
>>>  IBM JDK 1.5.0
>>>  Maven 2.2.1
>>>
>>>
>>> Thanks for any idea,
>>> Andreas
>>>
>>>
>>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> For additional commands, e-mail: users-h...@maven.apache.org
>>
>>
>>
>>
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>


Re: Compiler encoding on SuSE Linux

2010-10-18 Thread Andreas Simon

Thank you for your reply!

On my developer machine is Ubuntu 10.04. Same result when running Oracle 
JDK 1.6.0u21.

What are you running on your developer machine? Can you run it with Oracle JDK?

Cheers,
Per Hedman

On Mon, Oct 18, 2010 at 8:51 PM, Andreas Simon  wrote:
   

Hi all,

I got a quite strange problem with my tests. I have 3 tests that shall
control some messages for the user. These messages contain some German
umlauts (ä, ö, ü and ß). On my Ubuntu developer machine the tests run fine.
On my SuSE integration server the tests fail. The assertions fail with the
following message:

   expected:<...ü...>  but was:<...??...>

Obviously, the test files and the tested file are compiled with different
encodings.

I have tried several settings with UTF-8,




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


src-compile
compile

compile


1.5
1.5
UTF-8
true
UTF-8
UTF-8
-Dfile.encoding=utf8



default-compile
test-compile

testCompile


1.5
1.5
UTF-8
true
UTF-8
UTF-8
-Dfile.encoding=utf8




1.5
1.5
UTF-8
true
UTF-8
UTF-8
-Dfile.encoding=utf8






UTF-8
UTF-8


Some settings are redundant, but two are better than one. Any way, these
settings don't apply to the compiling of the test files. I have searched
some hours for similar problems, but I found no other solution. To be
complete, my configuration:

  SuSE 11.1
  IBM JDK 1.5.0
  Maven 2.2.1


Thanks for any idea,
Andreas

 

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


   



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



Re: Compiler encoding on SuSE Linux

2010-10-18 Thread per-henrik hedman
What are you running on your developer machine? Can you run it with Oracle JDK?

Cheers,
Per Hedman

On Mon, Oct 18, 2010 at 8:51 PM, Andreas Simon  wrote:
> Hi all,
>
> I got a quite strange problem with my tests. I have 3 tests that shall
> control some messages for the user. These messages contain some German
> umlauts (ä, ö, ü and ß). On my Ubuntu developer machine the tests run fine.
> On my SuSE integration server the tests fail. The assertions fail with the
> following message:
>
>   expected:<...ü...> but was:<...??...>
>
> Obviously, the test files and the tested file are compiled with different
> encodings.
>
> I have tried several settings with UTF-8,
>
> 
> 
> 
> org.apache.maven.plugins
> maven-compiler-plugin
> 2.3.2
> 
> 
> src-compile
> compile
> 
> compile
> 
> 
> 1.5
> 1.5
> UTF-8
> true
> UTF-8
> UTF-8
> -Dfile.encoding=utf8
> 
> 
> 
> default-compile
> test-compile
> 
> testCompile
> 
> 
> 1.5
> 1.5
> UTF-8
> true
> UTF-8
> UTF-8
> -Dfile.encoding=utf8
> 
> 
> 
> 
> 1.5
> 1.5
> UTF-8
> true
> UTF-8
> UTF-8
> -Dfile.encoding=utf8
> 
> 
> 
> 
>
> 
> UTF-8
> UTF-8
> 
>
> Some settings are redundant, but two are better than one. Any way, these
> settings don't apply to the compiling of the test files. I have searched
> some hours for similar problems, but I found no other solution. To be
> complete, my configuration:
>
>  SuSE 11.1
>  IBM JDK 1.5.0
>  Maven 2.2.1
>
>
> Thanks for any idea,
> Andreas
>

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



Compiler encoding on SuSE Linux

2010-10-18 Thread Andreas Simon

Hi all,

I got a quite strange problem with my tests. I have 3 tests that shall 
control some messages for the user. These messages contain some German 
umlauts (ä, ö, ü and ß). On my Ubuntu developer machine the tests run 
fine. On my SuSE integration server the tests fail. The assertions fail 
with the following message:


   expected:<...ü...> but was:<...??...>

Obviously, the test files and the tested file are compiled with 
different encodings.


I have tried several settings with UTF-8,




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


src-compile
compile

compile


1.5
1.5
UTF-8
true
UTF-8
UTF-8
-Dfile.encoding=utf8



default-compile
test-compile

testCompile


1.5
1.5
UTF-8
true
UTF-8
UTF-8
-Dfile.encoding=utf8




1.5
1.5
UTF-8
true
UTF-8
UTF-8
-Dfile.encoding=utf8






UTF-8
UTF-8


Some settings are redundant, but two are better than one. Any way, these 
settings don't apply to the compiling of the test files. I have searched 
some hours for similar problems, but I found no other solution. To be 
complete, my configuration:


  SuSE 11.1
  IBM JDK 1.5.0
  Maven 2.2.1


Thanks for any idea,
Andreas


Re: Maven 3.0 and checkstyle plugin

2010-10-18 Thread Dennis Lundberg
Yes, I thought it might be something like that. It is actually the
combination of Maven 3 and Maven Site Plugin 3 that is slightly
different in how it handles a reporting plugin's configuration, as
compared to Maven 2 and Maven Site Plugin 2.x.

On 2010-10-18 15:29, Thiessen, Todd (Todd) wrote:
> Solved it. The problem was I didn't include the  tag in the 
>  section. It was only included in the  section. Somehow, 
> this used to work in 2.2.1. I guess Maven 3.0 is tighter in this regard ;-).
> 
>> -Original Message-
>> From: Thiessen, Todd (Todd) [mailto:tthies...@avaya.com]
>> Sent: Monday, October 18, 2010 8:05 AM
>> To: Maven Users List
>> Subject: RE: Maven 3.0 and checkstyle plugin
>>
>> Thanks Dennis. Its from the build section. More specifically,
>> pluginmanagement.
>>
>> Thanks also for those links. I took a look at the compatibility matrix
>> and for checkstyle there is this jira:
>>
>> http://jira.codehaus.org/browse/MCHECKSTYLE-123
>>
>> Although it says it has been fixed as of 2.5. But the last comment from
>> Oliver states:
>>
>> "Leave it open as some its continue to failed with mvn 3.x"
>>
>> So I am not entirely sure if this means there is still a problem or if it
>> has been fixed ;-).
>>
>>> -Original Message-
>>> From: Dennis Lundberg [mailto:denn...@apache.org]
>>> Sent: Saturday, October 16, 2010 10:07 AM
>>> To: Maven Users List
>>> Subject: Re: Maven 3.0 and checkstyle plugin
>>>
>>> My guess is that your configuration is in the wrong place. Have you
>> read
>>> the "Maven 3 Compatibility Notes" and "Maven 3 and Site Plugin"?
>>>
>>>
>> https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+Compatibility
>>> +Notes
>>>
>>>
>> https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+and+site+plug
>>> in
>>>
>>> Is the snippet below from the  or from the  section
>> of
>>> your POM?
>>>
>>> On 2010-10-15 23:52, Thiessen, Todd (Todd) wrote:
 Is anyone else having trouble with the maven-checkstyle-plugin with
>>> maven 3.0? Specifically with using a custom rule set. The following
>>> snippet would find our custom rules in 2.2.1 but does not in 3.0.

 
   org.apache.maven.plugins
   maven-checkstyle-plugin
   2.6
   
  warning
  true
   
   
  
 checkstyle-main
 verify
 check
  
   
   
 
   groupid.of.rules
   artifactid.of.rules
   version.of.rules
 
   
 

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


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


-- 
Dennis Lundberg

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



Re: clean then package error

2010-10-18 Thread MK Tan
I should spell check before I sending this mail.

Maven need jdk and not jre.
And if possible please include environment variable called JAVA_HOME which
point to your jdk installation directory

2010/10/18 MK Tan 

> Haven require jdk but you are refer to jre
>
> On Oct 18, 2010 8:46 PM, "冯仁君"  wrote:
> > I'm new in using maven. when I try to package a helloworld maven program
> after I clean in the Eclipse IDE, it comes to an error. it says :
> >
> > [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile
> (default-compile) on project module: Compilation failure
> > Unable to locate the Javac Compiler in:
> > D:\Java\jre6\..\lib\tools.jar
> > Please ensure you are using JDK 1.4 or above and
> > not a JRE (the com.sun.tools.javac.Main class is required).
> > In most cases you can change the location of your Java
> > installation by setting the JAVA_HOME environment variable.
> > -> [Help 1]
> > [ERROR]
> > [ERROR] To see the full stack trace of the errors, re-run Maven with the
> -e switch.
> > [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> > [ERROR]
> > [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> > [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> > [ERROR]
> > [ERROR] After correcting the problems, you can resume the build with the
> command
> > [ERROR] mvn  -rf :module
> >
> > I'm sure I have installed the jdk1.6, and my environment variable is also
> correct. I don't it's the problem of maven, but I don't know what to do.
> what can I do?
>


Re: can clean plugin clean also local repository?

2010-10-18 Thread Jesse Farinacci
Greetings,

On Mon, Oct 18, 2010 at 11:14 AM, Daniele Dellafiore  wrote:
>
> It should be nice to tell mvn clean plugin to clean the local
> reposotory as well. What do you think? There is a way to do this? If
> not, is a patch for it interesting?
>

http://maven.apache.org/plugins/maven-dependency-plugin/purge-local-repository-mojo.html

-Jesse

-- 
There are 10 types of people in this world, those
that can read binary and those that can not.

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



can clean plugin clean also local repository?

2010-10-18 Thread Daniele Dellafiore
Hi.

It happens sometimes that something that should be broken in the build
continue to work because use a old dependency in the repository. Btw
works at half, but does not broke for the right reason or does not
broke at all when it should.
It happens for example after a refactoring of the modules, moving one
module from one project to another.

It should be nice to tell mvn clean plugin to clean the local
reposotory as well. What do you think? There is a way to do this? If
not, is a patch for it interesting?

-- 
Daniele Dellafiore
http://danieledellafiore.net

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



overriding inherited properties: what's the semantics?

2010-10-18 Thread Stephan Herrmann
I've observed some unexpected behavior when a declaration in a 
parent pom uses a property that is overridden in a child pom.

While waiting for parameterized mixins I'd love to know to what 
degree property overriding can actually simulate parameterization.

Is this a FAQ? Were should I search for a definition of the semantics?
Is evaluation order-dependent? If so, how exactly?

best,
Stephan


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



Maven and forked lifecycle

2010-10-18 Thread Luca DE PETRILLO
Hi,
i would like to ask if there is some way to prevent a plugin to fork the
Maven build without patch it.

I ask this because, in some projects, I need to attach to the build phase
some plugins that don't have the "no-fork" goals and, right now, them are
forcing maven to re-executes whole build portions, wasting a lot of time
and, in worst cases, creating mess with files generated during the normal
build phase.

Another thing that i can't understand, is why Maven should fork the build:
if a plugin that requires the generate:source phase is attached "after"
the generate:source phase execution, for which reason the generate:source
phase (and each previous phase) should be re-executed?

Thanks in advance,
Luca De Petrillo


RE: Maven 3.0 and checkstyle plugin

2010-10-18 Thread Thiessen, Todd (Todd)
Solved it. The problem was I didn't include the  tag in the 
 section. It was only included in the  section. Somehow, this 
used to work in 2.2.1. I guess Maven 3.0 is tighter in this regard ;-).

> -Original Message-
> From: Thiessen, Todd (Todd) [mailto:tthies...@avaya.com]
> Sent: Monday, October 18, 2010 8:05 AM
> To: Maven Users List
> Subject: RE: Maven 3.0 and checkstyle plugin
> 
> Thanks Dennis. Its from the build section. More specifically,
> pluginmanagement.
> 
> Thanks also for those links. I took a look at the compatibility matrix
> and for checkstyle there is this jira:
> 
> http://jira.codehaus.org/browse/MCHECKSTYLE-123
> 
> Although it says it has been fixed as of 2.5. But the last comment from
> Oliver states:
> 
> "Leave it open as some its continue to failed with mvn 3.x"
> 
> So I am not entirely sure if this means there is still a problem or if it
> has been fixed ;-).
> 
> > -Original Message-
> > From: Dennis Lundberg [mailto:denn...@apache.org]
> > Sent: Saturday, October 16, 2010 10:07 AM
> > To: Maven Users List
> > Subject: Re: Maven 3.0 and checkstyle plugin
> >
> > My guess is that your configuration is in the wrong place. Have you
> read
> > the "Maven 3 Compatibility Notes" and "Maven 3 and Site Plugin"?
> >
> >
> https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+Compatibility
> > +Notes
> >
> >
> https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+and+site+plug
> > in
> >
> > Is the snippet below from the  or from the  section
> of
> > your POM?
> >
> > On 2010-10-15 23:52, Thiessen, Todd (Todd) wrote:
> > > Is anyone else having trouble with the maven-checkstyle-plugin with
> > maven 3.0? Specifically with using a custom rule set. The following
> > snippet would find our custom rules in 2.2.1 but does not in 3.0.
> > >
> > > 
> > >   org.apache.maven.plugins
> > >   maven-checkstyle-plugin
> > >   2.6
> > >   
> > >  warning
> > >  true
> > >   
> > >   
> > >  
> > > checkstyle-main
> > > verify
> > > check
> > >  
> > >   
> > >   
> > > 
> > >   groupid.of.rules
> > >   artifactid.of.rules
> > >   version.of.rules
> > > 
> > >   
> > > 
> > >
> > > -
> > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> > > For additional commands, e-mail: users-h...@maven.apache.org
> > >
> > >
> >
> >
> > --
> > Dennis Lundberg
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> > For additional commands, e-mail: users-h...@maven.apache.org
> 
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org


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



Re: Error reading archetype catalog http://repo1.maven.org/maven2

2010-10-18 Thread Antonio Petrelli
2010/10/18 Marco Rossi :
> Ok, now works (after reading the comments to
> http://jira.codehaus.org/browse/ARCHETYPE-202).
> It's amazing that's this bug is currently open (in the repository my version
> is the latest one [
> http://mirrors.ibiblio.org/pub/mirrors/maven2/org/apache/maven/plugins/maven-archetype-plugin/
> ]).

The bug is closed, it's 2.0 version that is not yet released. Sorry, my fault.

Antonio

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



Re: Error reading archetype catalog http://repo1.maven.org/maven2

2010-10-18 Thread Marco Rossi
Ok, now works (after reading the comments to
http://jira.codehaus.org/browse/ARCHETYPE-202).
It's amazing that's this bug is currently open (in the repository my version
is the latest one [
http://mirrors.ibiblio.org/pub/mirrors/maven2/org/apache/maven/plugins/maven-archetype-plugin/
]).

Thanks guys!


Re: clean then package error

2010-10-18 Thread MK Tan
Haven require jdk but you are refer to jre

On Oct 18, 2010 8:46 PM, "冯仁君"  wrote:
> I'm new in using maven. when I try to package a helloworld maven program
after I clean in the Eclipse IDE, it comes to an error. it says :
>
> [ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile
(default-compile) on project module: Compilation failure
> Unable to locate the Javac Compiler in:
> D:\Java\jre6\..\lib\tools.jar
> Please ensure you are using JDK 1.4 or above and
> not a JRE (the com.sun.tools.javac.Main class is required).
> In most cases you can change the location of your Java
> installation by setting the JAVA_HOME environment variable.
> -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the
-e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions,
please read the following articles:
> [ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
command
> [ERROR] mvn  -rf :module
>
> I'm sure I have installed the jdk1.6, and my environment variable is also
correct. I don't it's the problem of maven, but I don't know what to do.
what can I do?


RE: Antwort: Re: RE: Maven *.ear build for SAP Web AS

2010-10-18 Thread Martin Gainty

Torsten

I just took a quick glance at the cargo deployment containers and noticed SAP 
was missing
 
 Directory of $m2_home/src/main/java/cargo/trunks/core/containers:
  geronimo
  glassfish
  jboss
  jetty
  jonas
  orion
  resin
  tomcat
  weblogic
 
  3,948 pom.xml

apparently SAP container was not considered during the initial development of 
cargo
if you could file a JIRA we could gauge the work involved to add SAP Container
https://jira.codehaus.org/browse/CARGO
 
thanks
Martin 
__ 
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité

Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger 
sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung 
oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem 
Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. 
Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung 
fuer den Inhalt uebernehmen.
Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le 
destinataire prévu, nous te demandons avec bonté que pour satisfaire informez 
l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est 
interdite. Ce message sert à l'information seulement et n'aura pas n'importe 
quel effet légalement obligatoire. Étant donné que les email peuvent facilement 
être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité 
pour le contenu fourni.



 

> To: users@maven.apache.org
> Subject: Antwort: Re: RE: Maven *.ear build for SAP Web AS
> From: torsten.reinh...@gi-de.com
> Date: Mon, 18 Oct 2010 14:26:04 +0200
> 
> that´s our opinion too:-)
> But the problem still exists and the only way to fix that is using a 
> sequence of ANT Tasks to manually "repairt" that..
> 
> Thanx anyway, 
> 
> Torsten
> 
> 
> 
> 
> Wayne Fay  
> 10.09.2010 16:06
> Bitte antworten an
> "Maven Users List" 
> 
> 
> An
> Maven Users List 
> Kopie
> 
> Thema
> Re: RE: Maven *.ear build for SAP Web AS
> 
> 
> 
> 
> 
> 
> > Here´s some more detailed information, where the same problem has
> > appeared:
> >
> > http://forums.sdn.sap.com/message.jspa?messageID=4753421
> 
> I've run into this with SAP Web AS (among with a great number of other
> "issues" in wars and ears that otherwise deploy with zero issues on
> all the other major app servers in the market) and all I can say is...
> don't use SAP Web AS unless you have a lot of time and patience to
> deal with these kinds of problems manually.
> 
> Wayne
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
> 
> 
  

Re: Error reading archetype catalog http://repo1.maven.org/maven2

2010-10-18 Thread Marco Rossi
Ok, thanks.
I have the  version 2.0-alpha-5.

Do you know how to update the release?


Re: Error reading archetype catalog http://repo1.maven.org/maven2

2010-10-18 Thread Alexey Direct
Example: mvn help:describe -Dplugin=archetype, for more information :
http://www.sonatype.com/books/mvnref-book/reference/installation-sect-help-plugin-install.html

2010/10/18 Marco Rossi 

> >And, are you behind a proxy? Did you set it in settings.xml?
> Yes, i set it. Indeed i see my local repository "increase"
>
> >If yes, are you using an archetype plugin version prior to 2.0?
> Honestly i don't know. I simply download maven 3.0, configure the proxy and
> try the simpler command
>
> mvn archetype:generate -DgroupId=com.mycompany.app \
> -DartifactId=my-app -DarchetypeArtifactId=maven-archetype-quickstart \
> -DinteractiveMode=false
>
> to start. Where can i find the "archetype plugin version"?
>
> On Mon, Oct 18, 2010 at 2:32 PM, Antonio Petrelli <
> antonio.petre...@gmail.com> wrote:
>
> > 2010/10/18 Alexey Direct :
> > > Hi Marco. Did you have internet connection at this time?
> >
> >
> > If yes, are you using an archetype plugin version prior to 2.0?
> > The last question is about this bug:
> > http://jira.codehaus.org/browse/ARCHETYPE-202
> >
> > Antonio
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> > For additional commands, e-mail: users-h...@maven.apache.org
> >
> >
>


clean then package error

2010-10-18 Thread 冯仁君
I'm new in using maven. when I try to package a helloworld maven program after 
I clean in the Eclipse IDE, it comes to an error. it says : 

[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile (default-compile) 
on project module: Compilation failure
Unable to locate the Javac Compiler in:
  D:\Java\jre6\..\lib\tools.jar
Please ensure you are using JDK 1.4 or above and
not a JRE (the com.sun.tools.javac.Main class is required).
In most cases you can change the location of your Java
installation by setting the JAVA_HOME environment variable.
-> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn  -rf :module

I'm sure I have installed the jdk1.6, and my environment variable is also 
correct. I don't it's the problem of maven, but I don't know what to do. what 
can I do?

Re: Error reading archetype catalog http://repo1.maven.org/maven2

2010-10-18 Thread Marco Rossi
>And, are you behind a proxy? Did you set it in settings.xml?
Yes, i set it. Indeed i see my local repository "increase"

>If yes, are you using an archetype plugin version prior to 2.0?
Honestly i don't know. I simply download maven 3.0, configure the proxy and
try the simpler command

mvn archetype:generate -DgroupId=com.mycompany.app \
-DartifactId=my-app -DarchetypeArtifactId=maven-archetype-quickstart \
-DinteractiveMode=false

to start. Where can i find the "archetype plugin version"?

On Mon, Oct 18, 2010 at 2:32 PM, Antonio Petrelli <
antonio.petre...@gmail.com> wrote:

> 2010/10/18 Alexey Direct :
> > Hi Marco. Did you have internet connection at this time?
>
>
> If yes, are you using an archetype plugin version prior to 2.0?
> The last question is about this bug:
> http://jira.codehaus.org/browse/ARCHETYPE-202
>
> Antonio
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>


Re: Maven 3 + Gwt 2.1 project

2010-10-18 Thread Olivier Lamy
2.1-SNAPSHOT

which is in

  


  google-snapshots
  https://oss.sonatype.org/content/repositories/google-snapshots/
  Google Web Toolkit Repository Snapshots
  
false
  
  
true
  

  

2010/10/18 Ron Wheeler :
>  Wrong version?
>
> com.google.gwt
> gwt-servlet
> ${gwt.version}
> runtime
>
> com.google.gwt
> gwt-servlet
> ${gxt.version}
> runtime
>
> Don't see 2.1.1 in Maven Central but do see 2.0.0
> Is 2.1.1 found somewhere else?
>
>
> Ron
>
> On 18/10/2010 5:20 AM, Xavier Carpentier wrote:
>>
>>  Hey,
>>
>> I work to migrate Gwt project (2.1-SNAPSHOT version) to maven project and
>> I have a problem on dependency.
>>
>> Exception : "org.apache.maven.lifecycle.LifecycleExecutionException:
>> Failed to execute goal org.codehaus.mojo:gwt-maven-plugin:1.2:compile
>> (default) on project com.***.***.ui: artifact not found - Failure to find
>> com.google.gwt:gwt-dev:jar:linux:2.1-SNAPSHOT in
>> http://repository.codehaus.org/org/codehaus/mojo/ was cached in the local
>> repository, resolution will not be reattempted until the update interval of
>> codehaus-maven-repo has elapsed or updates are forced"
>>
>> I use Maven 3.
>>
>> Why this error ? How can I repair this ?
>>
>> Look at my pom.xml :
>>
>> 
>> 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/maven-v4_0_0.xsd";>
>> 
>> 4.0.0
>> com.greenivory.greendget
>> com.greendget.rss.ui
>> war
>> 1.0-SNAPSHOT
>> RssReader
>> 
>>
>> 
>> 2.1-SNAPSHOT
>> 2.1.1
>>
>> 
>> 1.6
>> 1.6
>>
>> 
>>
>> 
>>
>> 
>> 
>> com.google.gwt
>> gwt-servlet
>> ${gwt.version}
>> runtime
>> 
>> 
>> com.google.gwt
>> gwt-user
>> ${gwt.version}
>> provided
>> 
>> 
>> com.greenivory.plumpeacock
>> com.***.***.sdk.ui
>> 1.0-SNAPSHOT
>> jar
>> provided
>> 
>> 
>> com.extjs
>> gxt
>> ${gxt.version}
>> jar
>> provided
>> 
>> 
>> 
>> junit
>> junit
>> 4.7
>> test
>> 
>> 
>>
>> 
>> 
>> codehaus-maven-repo
>> Codehaus repo
>> http://repository.codehaus.org/org/codehaus/mojo/
>> 
>> 
>> google-maven-snapshot-repository
>> Google Maven Snapshot Repository
>> https://oss.sonatype.org/content/repositories/google-snapshots
>> 
>> true
>> 
>> 
>>
>> 
>>
>> 
>> war/WEB-INF/classes
>> 
>> 
>> org.codehaus.mojo
>> gwt-maven-plugin
>> 1.2
>> 
>> 
>> 
>> compile
>> test
>> 
>> 
>> 
>> 
>> com.greendget.rss.ui.client.RssReader/Rss.html
>> 
>> 
>> 
>> org.apache.maven.plugins
>> maven-compiler-plugin
>> 2.0.2
>> 
>> ${maven.compiler.source}
>> ${maven.compiler.target}
>> 
>> 
>> 
>> 
>>
>> 
>>
>>
>> Regards,
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>



-- 
Olivier
http://twitter.com/olamy
http://www.linkedin.com/in/olamy

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



Antwort: Re: RE: Maven *.ear build for SAP Web AS

2010-10-18 Thread torsten . reinhard
that´s our opinion too:-)
But the problem still exists and the only way to fix that is using a 
sequence of ANT Tasks to manually "repairt" that..

Thanx anyway, 

Torsten
 



Wayne Fay  
10.09.2010 16:06
Bitte antworten an
"Maven Users List" 


An
Maven Users List 
Kopie

Thema
Re: RE: Maven *.ear build for SAP Web AS






>  Here´s some more detailed information, where the same problem has
> appeared:
>
> http://forums.sdn.sap.com/message.jspa?messageID=4753421

I've run into this with SAP Web AS (among with a great number of other
"issues" in wars and ears that otherwise deploy with zero issues on
all the other major app servers in the market) and all I can say is...
don't use SAP Web AS unless you have a lot of time and patience to
deal with these kinds of problems manually.

Wayne

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




Re: Error reading archetype catalog http://repo1.maven.org/maven2

2010-10-18 Thread Antonio Petrelli
2010/10/18 Alexey Direct :
> Hi Marco. Did you have internet connection at this time?

And, are you behind a proxy? Did you set it in settings.xml?
If yes, are you using an archetype plugin version prior to 2.0?
The last question is about this bug:
http://jira.codehaus.org/browse/ARCHETYPE-202

Antonio

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



Re: Error reading archetype catalog http://repo1.maven.org/maven2

2010-10-18 Thread Alexey Direct
Hi Marco. Did you have internet connection at this time?

I'm tried your command on Maven 3 from box(without any user's config). It
works fine.

2010/10/18 Marco Rossi 

> Hi,
> i'm newer with maven. I try to google but i don't fine the answer.
>
> Everytime i try a maven command, i.e.
> mvn archetype:generate -DgroupId=com.mycompany.app \
> -DartifactId=my-app -DarchetypeArtifactId=maven-archetype-quickstart \
> -DinteractiveMode=false
>
> i get the message in the title. What's wrong?
> i'm using maven 3.0, without mirrors (central repositoty).
>
> Thanks in advance,
> Marco
>


Error reading archetype catalog http://repo1.maven.org/maven2

2010-10-18 Thread Marco Rossi
Hi,
i'm newer with maven. I try to google but i don't fine the answer.

Everytime i try a maven command, i.e.
mvn archetype:generate -DgroupId=com.mycompany.app \
-DartifactId=my-app -DarchetypeArtifactId=maven-archetype-quickstart \
-DinteractiveMode=false

i get the message in the title. What's wrong?
i'm using maven 3.0, without mirrors (central repositoty).

Thanks in advance,
Marco


RE: Maven 3.0 and checkstyle plugin

2010-10-18 Thread Thiessen, Todd (Todd)
Thanks Dennis. Its from the build section. More specifically, pluginmanagement.

Thanks also for those links. I took a look at the compatibility matrix and for 
checkstyle there is this jira:

http://jira.codehaus.org/browse/MCHECKSTYLE-123

Although it says it has been fixed as of 2.5. But the last comment from Oliver 
states:

"Leave it open as some its continue to failed with mvn 3.x"

So I am not entirely sure if this means there is still a problem or if it has 
been fixed ;-).

> -Original Message-
> From: Dennis Lundberg [mailto:denn...@apache.org]
> Sent: Saturday, October 16, 2010 10:07 AM
> To: Maven Users List
> Subject: Re: Maven 3.0 and checkstyle plugin
> 
> My guess is that your configuration is in the wrong place. Have you read
> the "Maven 3 Compatibility Notes" and "Maven 3 and Site Plugin"?
> 
> https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+Compatibility
> +Notes
> 
> https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+and+site+plug
> in
> 
> Is the snippet below from the  or from the  section of
> your POM?
> 
> On 2010-10-15 23:52, Thiessen, Todd (Todd) wrote:
> > Is anyone else having trouble with the maven-checkstyle-plugin with
> maven 3.0? Specifically with using a custom rule set. The following
> snippet would find our custom rules in 2.2.1 but does not in 3.0.
> >
> > 
> >   org.apache.maven.plugins
> >   maven-checkstyle-plugin
> >   2.6
> >   
> >  warning
> >  true
> >   
> >   
> >  
> > checkstyle-main
> > verify
> > check
> >  
> >   
> >   
> > 
> >   groupid.of.rules
> >   artifactid.of.rules
> >   version.of.rules
> > 
> >   
> > 
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> > For additional commands, e-mail: users-h...@maven.apache.org
> >
> >
> 
> 
> --
> Dennis Lundberg
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org


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



Re: Maven 3 + Gwt 2.1 project

2010-10-18 Thread Xavier Carpentier

 Hey,
${gxt.version} 2.1.1 it's GXT version :

com.extjs
gxt
${gxt.version}
jar

Not Gwt !

Bye,

On 18/10/2010 13:53, Ron Wheeler wrote:

 Wrong version?

com.google.gwt
gwt-servlet
${gwt.version}
runtime

com.google.gwt
gwt-servlet
${gxt.version}
runtime

Don't see 2.1.1 in Maven Central but do see 2.0.0
Is 2.1.1 found somewhere else?


Ron

On 18/10/2010 5:20 AM, Xavier Carpentier wrote:

 Hey,

I work to migrate Gwt project (2.1-SNAPSHOT version) to maven project 
and I have a problem on dependency.


Exception : "org.apache.maven.lifecycle.LifecycleExecutionException: 
Failed to execute goal org.codehaus.mojo:gwt-maven-plugin:1.2:compile 
(default) on project com.***.***.ui: artifact not found - Failure to 
find com.google.gwt:gwt-dev:jar:linux:2.1-SNAPSHOT in 
http://repository.codehaus.org/org/codehaus/mojo/ was cached in the 
local repository, resolution will not be reattempted until the update 
interval of codehaus-maven-repo has elapsed or updates are forced"


I use Maven 3.

Why this error ? How can I repair this ?

Look at my pom.xml :


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/maven-v4_0_0.xsd";>


4.0.0
com.greenivory.greendget
com.greendget.rss.ui
war
1.0-SNAPSHOT
RssReader



2.1-SNAPSHOT
2.1.1


1.6
1.6







com.google.gwt
gwt-servlet
${gwt.version}
runtime


com.google.gwt
gwt-user
${gwt.version}
provided


com.greenivory.plumpeacock
com.***.***.sdk.ui
1.0-SNAPSHOT
jar
provided


com.extjs
gxt
${gxt.version}
jar
provided



junit
junit
4.7
test





codehaus-maven-repo
Codehaus repo
http://repository.codehaus.org/org/codehaus/mojo/


google-maven-snapshot-repository
Google Maven Snapshot Repository
https://oss.sonatype.org/content/repositories/google-snapshots 



true






war/WEB-INF/classes


org.codehaus.mojo
gwt-maven-plugin
1.2



compile
test




com.greendget.rss.ui.client.RssReader/Rss.html



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

${maven.compiler.source}
${maven.compiler.target}








Regards,



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





--

Carpentier Xavier
Ingénieur Développement - x.carpent...@greenivory.com 
 - http://www.greenivory.com 



*GreenIvory Europe*
10 rue Saint Wendelin
67500 Haguenau
France  *GreenIvory America*
Suite 200
3608 Shannon Road
Durham NC 27707
USA
Tél.+33 9 50 53 10 34   Tel.+1 (617) 862-2319
Fax +33 9 50 53 10 34   Fax +1 (919) 493-8837
GSM +33 6 68 81 87 68

Consider the environment. Don't print this e-mail unless you need to.
To avoid excessive data transfer, we've removed our logo.



Re: Maven 3 + Gwt 2.1 project

2010-10-18 Thread Ron Wheeler

 Wrong version?

com.google.gwt
gwt-servlet
${gwt.version}
runtime

com.google.gwt
gwt-servlet
${gxt.version}
runtime

Don't see 2.1.1 in Maven Central but do see 2.0.0
Is 2.1.1 found somewhere else?


Ron

On 18/10/2010 5:20 AM, Xavier Carpentier wrote:

 Hey,

I work to migrate Gwt project (2.1-SNAPSHOT version) to maven project 
and I have a problem on dependency.


Exception : "org.apache.maven.lifecycle.LifecycleExecutionException: 
Failed to execute goal org.codehaus.mojo:gwt-maven-plugin:1.2:compile 
(default) on project com.***.***.ui: artifact not found - Failure to 
find com.google.gwt:gwt-dev:jar:linux:2.1-SNAPSHOT in 
http://repository.codehaus.org/org/codehaus/mojo/ was cached in the 
local repository, resolution will not be reattempted until the update 
interval of codehaus-maven-repo has elapsed or updates are forced"


I use Maven 3.

Why this error ? How can I repair this ?

Look at my pom.xml :


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/maven-v4_0_0.xsd";>


4.0.0
com.greenivory.greendget
com.greendget.rss.ui
war
1.0-SNAPSHOT
RssReader



2.1-SNAPSHOT
2.1.1


1.6
1.6







com.google.gwt
gwt-servlet
${gwt.version}
runtime


com.google.gwt
gwt-user
${gwt.version}
provided


com.greenivory.plumpeacock
com.***.***.sdk.ui
1.0-SNAPSHOT
jar
provided


com.extjs
gxt
${gxt.version}
jar
provided



junit
junit
4.7
test





codehaus-maven-repo
Codehaus repo
http://repository.codehaus.org/org/codehaus/mojo/


google-maven-snapshot-repository
Google Maven Snapshot Repository
https://oss.sonatype.org/content/repositories/google-snapshots

true






war/WEB-INF/classes


org.codehaus.mojo
gwt-maven-plugin
1.2



compile
test




com.greendget.rss.ui.client.RssReader/Rss.html



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

${maven.compiler.source}
${maven.compiler.target}








Regards,



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



Re: Maven 3 + Gwt 2.1 project

2010-10-18 Thread Olivier Lamy
So I have added a temporary hack (until gwt 2.1.0 is released).
gwt-maven-plugin 2.1-SNAPSHOT are now available in
https://nexus.codehaus.org/content/groups/snapshots-group

2010/10/18 Olivier Lamy :
> Hi,
> This should more a question for mojo users.
> But I can answer here.
> The current gwt maven plugin need the gwt artifacts SNAPSHOT and this
> means the pom must contains a SNAPSHOT repository :
> https://oss.sonatype.org/content/repositories/google-snapshots/
> But the mojo parent pom thru an enforcer rule prevents using SNAPSHOT
> repositories :-(
> The solution for you is to build locally the mojo :
> svn co https://svn.codehaus.org/mojo/trunk/mojo/gwt-maven-plugin && cd
> gwt-maven-plugin && mvn clean install
>
>
>
>
> 2010/10/18 Xavier Carpentier :
>>  Hey,
>>
>> I work to migrate Gwt project (2.1-SNAPSHOT version) to maven project and I
>> have a problem on dependency.
>>
>> Exception : "org.apache.maven.lifecycle.LifecycleExecutionException: Failed
>> to execute goal org.codehaus.mojo:gwt-maven-plugin:1.2:compile (default) on
>> project com.***.***.ui: artifact not found - Failure to find
>> com.google.gwt:gwt-dev:jar:linux:2.1-SNAPSHOT in
>> http://repository.codehaus.org/org/codehaus/mojo/ was cached in the local
>> repository, resolution will not be reattempted until the update interval of
>> codehaus-maven-repo has elapsed or updates are forced"
>>
>> I use Maven 3.
>>
>> Why this error ? How can I repair this ?
>>
>> Look at my pom.xml :
>>
>> 
>> 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/maven-v4_0_0.xsd";>
>> 
>> 4.0.0
>> com.greenivory.greendget
>> com.greendget.rss.ui
>> war
>> 1.0-SNAPSHOT
>> RssReader
>> 
>>
>> 
>> 2.1-SNAPSHOT
>> 2.1.1
>>
>> 
>> 1.6
>> 1.6
>>
>> 
>>
>> 
>>
>> 
>> 
>> com.google.gwt
>> gwt-servlet
>> ${gwt.version}
>> runtime
>> 
>> 
>> com.google.gwt
>> gwt-user
>> ${gwt.version}
>> provided
>> 
>> 
>> com.greenivory.plumpeacock
>> com.***.***.sdk.ui
>> 1.0-SNAPSHOT
>> jar
>> provided
>> 
>> 
>> com.extjs
>> gxt
>> ${gxt.version}
>> jar
>> provided
>> 
>> 
>> 
>> junit
>> junit
>> 4.7
>> test
>> 
>> 
>>
>> 
>> 
>> codehaus-maven-repo
>> Codehaus repo
>> http://repository.codehaus.org/org/codehaus/mojo/
>> 
>> 
>> google-maven-snapshot-repository
>> Google Maven Snapshot Repository
>> https://oss.sonatype.org/content/repositories/google-snapshots
>> 
>> true
>> 
>> 
>>
>> 
>>
>> 
>> war/WEB-INF/classes
>> 
>> 
>> org.codehaus.mojo
>> gwt-maven-plugin
>> 1.2
>> 
>> 
>> 
>> compile
>> test
>> 
>> 
>> 
>> 
>> com.greendget.rss.ui.client.RssReader/Rss.html
>> 
>> 
>> 
>> org.apache.maven.plugins
>> maven-compiler-plugin
>> 2.0.2
>> 
>> ${maven.compiler.source}
>> ${maven.compiler.target}
>> 
>> 
>> 
>> 
>>
>> 
>>
>>
>> Regards,
>> --
>>
>> Carpentier Xavier
>> Ingénieur Développement - x.carpent...@greenivory.com
>>  - http://www.greenivory.com
>> 
>>
>> *GreenIvory Europe*
>> 10 rue Saint Wendelin
>> 67500 Haguenau
>> France  *GreenIvory America*
>> Suite 200
>> 3608 Shannon Road
>> Durham NC 27707
>> USA
>> Tél.    +33 9 50 53 10 34       Tel.    +1 (617) 862-2319
>> Fax     +33 9 50 53 10 34       Fax     +1 (919) 493-8837
>> GSM     +33 6 68 81 87 68
>>
>> Consider the environment. Don't print this e-mail unless you need to.
>> To avoid excessive data transfer, we've removed our logo.
>>
>>
>
>
>
> --
> Olivier
> http://twitter.com/olamy
> http://www.linkedin.com/in/olamy
>



-- 
Olivier
http://twitter.com/olamy
http://www.linkedin.com/in/olamy

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



Re: Maven 3 + Gwt 2.1 project

2010-10-18 Thread Olivier Lamy
Hi,
This should more a question for mojo users.
But I can answer here.
The current gwt maven plugin need the gwt artifacts SNAPSHOT and this
means the pom must contains a SNAPSHOT repository :
https://oss.sonatype.org/content/repositories/google-snapshots/
But the mojo parent pom thru an enforcer rule prevents using SNAPSHOT
repositories :-(
The solution for you is to build locally the mojo :
svn co https://svn.codehaus.org/mojo/trunk/mojo/gwt-maven-plugin && cd
gwt-maven-plugin && mvn clean install




2010/10/18 Xavier Carpentier :
>  Hey,
>
> I work to migrate Gwt project (2.1-SNAPSHOT version) to maven project and I
> have a problem on dependency.
>
> Exception : "org.apache.maven.lifecycle.LifecycleExecutionException: Failed
> to execute goal org.codehaus.mojo:gwt-maven-plugin:1.2:compile (default) on
> project com.***.***.ui: artifact not found - Failure to find
> com.google.gwt:gwt-dev:jar:linux:2.1-SNAPSHOT in
> http://repository.codehaus.org/org/codehaus/mojo/ was cached in the local
> repository, resolution will not be reattempted until the update interval of
> codehaus-maven-repo has elapsed or updates are forced"
>
> I use Maven 3.
>
> Why this error ? How can I repair this ?
>
> Look at my pom.xml :
>
> 
> 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/maven-v4_0_0.xsd";>
> 
> 4.0.0
> com.greenivory.greendget
> com.greendget.rss.ui
> war
> 1.0-SNAPSHOT
> RssReader
> 
>
> 
> 2.1-SNAPSHOT
> 2.1.1
>
> 
> 1.6
> 1.6
>
> 
>
> 
>
> 
> 
> com.google.gwt
> gwt-servlet
> ${gwt.version}
> runtime
> 
> 
> com.google.gwt
> gwt-user
> ${gwt.version}
> provided
> 
> 
> com.greenivory.plumpeacock
> com.***.***.sdk.ui
> 1.0-SNAPSHOT
> jar
> provided
> 
> 
> com.extjs
> gxt
> ${gxt.version}
> jar
> provided
> 
> 
> 
> junit
> junit
> 4.7
> test
> 
> 
>
> 
> 
> codehaus-maven-repo
> Codehaus repo
> http://repository.codehaus.org/org/codehaus/mojo/
> 
> 
> google-maven-snapshot-repository
> Google Maven Snapshot Repository
> https://oss.sonatype.org/content/repositories/google-snapshots
> 
> true
> 
> 
>
> 
>
> 
> war/WEB-INF/classes
> 
> 
> org.codehaus.mojo
> gwt-maven-plugin
> 1.2
> 
> 
> 
> compile
> test
> 
> 
> 
> 
> com.greendget.rss.ui.client.RssReader/Rss.html
> 
> 
> 
> org.apache.maven.plugins
> maven-compiler-plugin
> 2.0.2
> 
> ${maven.compiler.source}
> ${maven.compiler.target}
> 
> 
> 
> 
>
> 
>
>
> Regards,
> --
>
> Carpentier Xavier
> Ingénieur Développement - x.carpent...@greenivory.com
>  - http://www.greenivory.com
> 
>
> *GreenIvory Europe*
> 10 rue Saint Wendelin
> 67500 Haguenau
> France  *GreenIvory America*
> Suite 200
> 3608 Shannon Road
> Durham NC 27707
> USA
> Tél.    +33 9 50 53 10 34       Tel.    +1 (617) 862-2319
> Fax     +33 9 50 53 10 34       Fax     +1 (919) 493-8837
> GSM     +33 6 68 81 87 68
>
> Consider the environment. Don't print this e-mail unless you need to.
> To avoid excessive data transfer, we've removed our logo.
>
>



-- 
Olivier
http://twitter.com/olamy
http://www.linkedin.com/in/olamy

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



Re: Maven 3 + Gwt 2.1 project

2010-10-18 Thread kristian
is that your artifact-id ?
com.***.***.sdk.ui

if yes than I would guess the ***.*** are the problem.

regards, Kristian

On Mon, Oct 18, 2010 at 2:50 PM, Xavier Carpentier
 wrote:
>  Hey,
>
> I work to migrate Gwt project (2.1-SNAPSHOT version) to maven project and I
> have a problem on dependency.
>
> Exception : "org.apache.maven.lifecycle.LifecycleExecutionException: Failed
> to execute goal org.codehaus.mojo:gwt-maven-plugin:1.2:compile (default) on
> project com.***.***.ui: artifact not found - Failure to find
> com.google.gwt:gwt-dev:jar:linux:2.1-SNAPSHOT in
> http://repository.codehaus.org/org/codehaus/mojo/ was cached in the local
> repository, resolution will not be reattempted until the update interval of
> codehaus-maven-repo has elapsed or updates are forced"
>
> I use Maven 3.
>
> Why this error ? How can I repair this ?
>
> Look at my pom.xml :
>
> 
> 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/maven-v4_0_0.xsd";>
> 
> 4.0.0
> com.greenivory.greendget
> com.greendget.rss.ui
> war
> 1.0-SNAPSHOT
> RssReader
> 
>
> 
> 2.1-SNAPSHOT
> 2.1.1
>
> 
> 1.6
> 1.6
>
> 
>
> 
>
> 
> 
> com.google.gwt
> gwt-servlet
> ${gwt.version}
> runtime
> 
> 
> com.google.gwt
> gwt-user
> ${gwt.version}
> provided
> 
> 
> com.greenivory.plumpeacock
> com.***.***.sdk.ui
> 1.0-SNAPSHOT
> jar
> provided
> 
> 
> com.extjs
> gxt
> ${gxt.version}
> jar
> provided
> 
> 
> 
> junit
> junit
> 4.7
> test
> 
> 
>
> 
> 
> codehaus-maven-repo
> Codehaus repo
> http://repository.codehaus.org/org/codehaus/mojo/
> 
> 
> google-maven-snapshot-repository
> Google Maven Snapshot Repository
> https://oss.sonatype.org/content/repositories/google-snapshots
> 
> true
> 
> 
>
> 
>
> 
> war/WEB-INF/classes
> 
> 
> org.codehaus.mojo
> gwt-maven-plugin
> 1.2
> 
> 
> 
> compile
> test
> 
> 
> 
> 
> com.greendget.rss.ui.client.RssReader/Rss.html
> 
> 
> 
> org.apache.maven.plugins
> maven-compiler-plugin
> 2.0.2
> 
> ${maven.compiler.source}
> ${maven.compiler.target}
> 
> 
> 
> 
>
> 
>
>
> Regards,
> --
>
> Carpentier Xavier
> Ingénieur Développement - x.carpent...@greenivory.com
>  - http://www.greenivory.com
> 
>
> *GreenIvory Europe*
> 10 rue Saint Wendelin
> 67500 Haguenau
> France  *GreenIvory America*
> Suite 200
> 3608 Shannon Road
> Durham NC 27707
> USA
> Tél.    +33 9 50 53 10 34       Tel.    +1 (617) 862-2319
> Fax     +33 9 50 53 10 34       Fax     +1 (919) 493-8837
> GSM     +33 6 68 81 87 68
>
> Consider the environment. Don't print this e-mail unless you need to.
> To avoid excessive data transfer, we've removed our logo.
>
>

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



Maven 3 + Gwt 2.1 project

2010-10-18 Thread Xavier Carpentier

 Hey,

I work to migrate Gwt project (2.1-SNAPSHOT version) to maven project 
and I have a problem on dependency.


Exception : "org.apache.maven.lifecycle.LifecycleExecutionException: 
Failed to execute goal org.codehaus.mojo:gwt-maven-plugin:1.2:compile 
(default) on project com.***.***.ui: artifact not found - Failure to 
find com.google.gwt:gwt-dev:jar:linux:2.1-SNAPSHOT in 
http://repository.codehaus.org/org/codehaus/mojo/ was cached in the 
local repository, resolution will not be reattempted until the update 
interval of codehaus-maven-repo has elapsed or updates are forced"


I use Maven 3.

Why this error ? How can I repair this ?

Look at my pom.xml :


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/maven-v4_0_0.xsd";>


4.0.0
com.greenivory.greendget
com.greendget.rss.ui
war
1.0-SNAPSHOT
RssReader



2.1-SNAPSHOT
2.1.1


1.6
1.6







com.google.gwt
gwt-servlet
${gwt.version}
runtime


com.google.gwt
gwt-user
${gwt.version}
provided


com.greenivory.plumpeacock
com.***.***.sdk.ui
1.0-SNAPSHOT
jar
provided


com.extjs
gxt
${gxt.version}
jar
provided



junit
junit
4.7
test





codehaus-maven-repo
Codehaus repo
http://repository.codehaus.org/org/codehaus/mojo/


google-maven-snapshot-repository
Google Maven Snapshot Repository
https://oss.sonatype.org/content/repositories/google-snapshots

true






war/WEB-INF/classes


org.codehaus.mojo
gwt-maven-plugin
1.2



compile
test




com.greendget.rss.ui.client.RssReader/Rss.html



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

${maven.compiler.source}
${maven.compiler.target}








Regards,
--

Carpentier Xavier
Ingénieur Développement - x.carpent...@greenivory.com 
 - http://www.greenivory.com 



*GreenIvory Europe*
10 rue Saint Wendelin
67500 Haguenau
France  *GreenIvory America*
Suite 200
3608 Shannon Road
Durham NC 27707
USA
Tél.+33 9 50 53 10 34   Tel.+1 (617) 862-2319
Fax +33 9 50 53 10 34   Fax +1 (919) 493-8837
GSM +33 6 68 81 87 68

Consider the environment. Don't print this e-mail unless you need to.
To avoid excessive data transfer, we've removed our logo.