date:20071026


I have the same problem!

Modifying the java sources putting direclty the unicode string IS NOT A
CLEVER SOLUTION.

Any other hints?

Thanks and best regards.
Raffaele



Luca Gmail wrote:
 
 The file is the same :)
 
 
 
 Tnx for your answer.
 
 
 On 6/19/06, Thorsten Heit [EMAIL PROTECTED] wrote:

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 Hi Luca,

  when i try to compile my project i have this error :
 
  duplicate case label error.
 
  Below the code where the error is raised:
 
  for (int i = 0; i  n; i++) {
 
   char c = s.charAt(i);
 
   switch (c) {
 
  case '': sb.append(lt;); break;
 
  case '': sb.append(gt;); break;
 
  case '': sb.append(amp;); break;
 
  case '': sb.append(quot;); break;
 
  case 'à': sb.append(agrave;);break;
 
  case 'À': sb.append(Agrave;);break;
 
  case 'â': sb.append(acirc;);break;
 
  case 'Â': sb.append(Acirc;);break;
 
  case 'ä': sb.append(auml;);break;
 
  case 'Ä': sb.append(Auml;);break;
 
  case 'å': sb.append(aring;);break;
 
  case 'Å': sb.append(Aring;);break;
 
  case 'æ': sb.append(aelig;);break;
 
  case 'Æ': sb.append(AElig;);break;
 
  case 'ç': sb.append(ccedil;);break;
 
  …
 
 
 
  In all the line.
 
  I compiled in windows machine and all works fine.
 
  I try ti compile in my linux machine and I have that error.

 That's a simple encoding problem in source code files - you're using
 non-ASCII characters in the above Java code... (have a look into your
 file on a Windows machine and then on a Linux box; it probably looks
 different)

 If you really have to use non-ASCII characters in a text file
 (properties file, Java source code etc.), you'd better use unicode
 notation instead (\u00E6 for æ  etc.).


 HTH

 Thorsten
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1.4.3 (MingW32)

 iD8DBQFElqUbQvObkgCcDe0RAteCAKCowelIRFulB1FgK28SK4ZY1IUaYwCfRKAT
 X4JHDYpMoeKB54pS12C30Kc=
 =TonV
 -END PGP SIGNATURE-

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


 
 

-- 
View this message in context: 
http://www.nabble.com/maven.compile.encoding-problem-%28-%29-tf1811337s177.html#a13423901
Sent from the Maven - Users mailing list archive at Nabble.com.


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

How to use different databases for tests and the actual application?

2007-10-26 Thread jimpo


I am using Maven2 to build my war packet. Base maven configuration is created
with Appfuse http://appfuse.org/display/APF/Home.

When I do a mvn install (or mvn cargo:deploy), first a test phase executes,
and then the final war is built and installed in the repository (or deployed
to my app server).

I want to run the tests against a different db than which the final package
uses. So far I have not figured out how to do this. Test phase uses the same
database as the final application.

I figured out how to use profiles to switch between different databases. I
can switch to test profile with, say, mvn test -Ptestdatabase. I could of
course use mvn test -Ptestdatabase to test and then separate command mvn
install -Dmaven.test.skip -Prealdatabase for creating the packet (and
skipping tests), but that's not very nice. I want to be able to issue one
command which does both phases, tests and packaging.

I am guessing maybe the solution would be something like activating profile
X for the tests phase, and then activating a different profile Y for the
actual build. How could I accomplish this?

-- 
View this message in context: 
http://www.nabble.com/How-to-use-different-databases-for-tests-and-the-actual-application--tf4696771s177.html#a13425450
Sent from the Maven - Users mailing list archive at Nabble.com.


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

Re: Building Eclipse plugins with Maven 2

2007-10-26 Thread Sebastien ARBOGAST

I finally found some lead to progress.
I managed to build and install the original version of the mojos.
Then I found something: it's all a problem of dependency versions. In my
source-plugin module manifest dependencies, I did not specify any version
for the plugins on which I depend, which caused the modified pom to
reference 1.0 version by default.
Now I added a version for the plugins that are in my workspace
(source-plugin et binary-plugin) and it's looking for the right versions.
But I still have a problem for plugins that are supposed to be provided by
Eclipse itself. It seems that they are not deployed to my local repository
or it's looking in the wrong directories:

1) com.mycompany.eclipse:org.eclipse.ui.ide:pom:1.0
  Path to dependency:
1)
com.mycompany.eclipse:com.mycompany.framework.eclipse.rcp:source-pl
ugin:1.0-SNAPSHOT
2) com.mycompany.eclipse:org.eclipse.ui.ide:pom:1.0

Obviously some bits and pieces are missing.

2007/10/26, Sebastien ARBOGAST [EMAIL PROTECTED] :

 OK, I really need this to work because I'm fed up with ant maintenance and
 manual dependency management.

 I've tried to start all over again. I think the problem might have come
 from the fact that I was not using the original version of the mojos
 described by the author of the article, but one that I found on m2eclipse
 repository. Do I downloaded the original version linked in the article, but
 when I tried to build it, it failed because it doesn't find maven-pst parent
 project. Does anyone know where I can fin that project?

 2007/10/23, Sebastien ARBOGAST [EMAIL PROTECTED] :
 
  I checked out the last version I could find in the m2eclipse project: 
  http://svn.codehaus.org/m2eclipse/maven-pst
 
 
  That's the one I'm using with a few modifications to the POM in order to
  build against Maven 2.0.7 and Eclipse 3.3.1
 
  Now here are the error messages that I get:
 
  [INFO]
  
  [ERROR] BUILD ERROR
  [INFO]
  
  [INFO] Failed to resolve artifact.
 
  Missing:
  --
  1) com.myapp.eclipse:org.springframework.spring:pom:1.0
Path to dependency:
  1) com.myapp.eclipse:com.myapp.framework.eclipse.rcp:source-pl
  ugin:1.0-SNAPSHOT
  2) com.myapp.eclipse:org.springframework.spring:pom:1.0
 
  2) com.myapp.eclipse:org.eclipse.core.databinding:pom:1.0
Path to dependency:
  1) com.myapp.eclipse:com.myapp.framework.eclipse.rcp:source-pl
  ugin:1.0-SNAPSHOT
  2) com.myapp.eclipse:org.eclipse.core.databinding:pom:1.0
 
  3) com.myapp.eclipse:org.apache.log4j:pom:1.0
Path to dependency:
  1) com.myapp.eclipse:com.myapp.framework.eclipse.rcp:source-pl
  ugin:1.0-SNAPSHOT
  2) com.myapp.eclipse:org.apache.log4j:pom:1.0
 
  4) com.myapp.eclipse:com.myapp.framework.common:pom:1.0-SNAPSHOT
Path to dependency:
  1) com.myapp.eclipse:com.myapp.framework.eclipse.rcp:source-pl
  ugin:1.0-SNAPSHOT
  2) com.myapp.eclipse:com.myapp.framework.common:pom:1.0-SNAPSH
  OT
 
  5) com.myapp.eclipse:org.eclipse.ui:jar:1.0
 
Try downloading the file manually from the project website.
 
Then, install it using the command:
mvn install:install-file -DgroupId=com.myapp.eclipse-DartifactId=org
  .eclipse.ui \
-Dversion=1.0 -Dpackaging=jar -Dfile=/path/to/file
 
Path to dependency:
  1) com.myapp.eclipse:com.myapp.framework.eclipse.rcp:source-pl
  ugin:1.0-SNAPSHOT
  2) com.myapp.eclipse:org.eclipse.ui:jar:1.0
 
  6) com.myapp.eclipse:org.eclipse.core.runtime:jar:1.0
 
Try downloading the file manually from the project website.
 
Then, install it using the command:
mvn install:install-file -DgroupId=com.myapp.eclipse-DartifactId=org
  .eclipse.core.runtime \
-Dversion=1.0 -Dpackaging=jar -Dfile=/path/to/file
 
Path to dependency:
  1) com.myapp.eclipse:com.myapp.framework.eclipse.rcp:source-pl
  ugin:1.0-SNAPSHOT
  2) com.myapp.eclipse:org.eclipse.core.runtime:jar:1.0
 
  7) com.myapp.eclipse:org.eclipse.jface.databinding:pom:1.0
Path to dependency:
  1) com.myapp.eclipse:com.myapp.framework.eclipse.rcp:source-pl
  ugin:1.0-SNAPSHOT
  2) com.myapp.eclipse:org.eclipse.jface.databinding:pom:1.0
 
  8) com.myapp.eclipse:com.myapp.security.crypto.smartcard:pom:1.0-SNAPS
  HOT
Path to dependency:
  1) com.myapp.eclipse:com.myapp.framework.eclipse.rcp:source-pl
  ugin:1.0-SNAPSHOT
  2) com.myapp.eclipse:com.myapp.security.crypto.smartcard:pom:1
  .0-SNAPSHOT
 
  9) com.myapp.eclipse:org.eclipse.ui.ide:pom:1.0
Path to dependency:
  1) com.myapp.eclipse:com.myapp.framework.eclipse.rcp:source-pl
  ugin:1.0-SNAPSHOT
  2) com.myapp.eclipse:org.eclipse.ui.ide:pom:1.0
 
  10) com.myapp.eclipse:org.eclipse.draw2d:pom:1.0
Path to dependency:
  1)

RE: Issues with recent update of maven-changes-plugin

2007-10-26 Thread LAMY Olivier

Have you try with force the  maven-changes-plugin version to 2.0-beta-2 or 
using a mvn version = 2.0.6 ?

--
Olivier

-Message d'origine-
De : Geraud Geraud [mailto:[EMAIL PROTECTED] 
Envoyé : vendredi 26 octobre 2007 12:32
À : Maven Users List
Objet : Issues with recent update of maven-changes-plugin

Hi,

it seems that the maven-metadata.xml at repo1.maven.org is incomplete
: it doesn't refer to the version 2.0-beta-2, so I cannot build maven site on 
my project (because I'm using Maven 2.0.5).

The error is:
[INFO] Ignoring available plugin update: 2.0-beta-3 as it requires Maven 
version 2.0.6 [INFO] 

[ERROR] BUILD ERROR
[INFO] 
[INFO] The plugin 'org.apache.maven.plugins:maven-changes-plugin' does not 
exist or no valid version could be found


Can anyone help?
Thanks.
--
Géraud

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


This e-mail, any attachments and the information contained therein (this 
message) are confidential and intended solely for the use of the addressee(s). 
If you have received this message in error please send it back to the sender 
and delete it. Unauthorized publication, use, dissemination or disclosure of 
this message, either in whole or in part is strictly prohibited.
--
Ce message électronique et tous les fichiers joints ainsi que  les informations 
contenues dans ce message ( ci après le message ), sont confidentiels et 
destinés exclusivement à l'usage de la  personne à laquelle ils sont adressés. 
Si vous avez reçu ce message par erreur, merci  de le renvoyer à son émetteur 
et de le détruire. Toutes diffusion, publication, totale ou partielle ou 
divulgation sous quelque forme que se soit non expressément autorisées de ce 
message, sont interdites.
-


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

dependencies outside maven

  Hello !

  Does anyone knows how to work with dependencies not managed by maven
? Is it possible to add a jar to the class path with its absolute path
on disk, instead of having maven fetch it automagically in the maven
repo ?

  Before you call me crazy, let's me explain why :

  I'm working in a large organization, thinking of moving to maven. We
have lots of projects, having lots of dependencies between them. For
the moment, those projects are deployed in a central, proprietary
repository. We have ant scripts taking care of downloading the jars
needed by a project.

  We need to be able to transition to maven one project after another
(we cant just stop working for one month ;-). So we need to be able to
still refer to our old proprietary repository if we move a project
to maven but not all its dependencies are managed by maven.

  Ideas I had sofar :

* Adding some ant script that will copy the needed dependencies to a
local repository. Problem : we also need to create a pom in the local
repo (and I cant see how to easily generate it automagically).
* Pull the dependencies out of the maven dependency management, and
add them manually to the maven classpath. Problem : I dont even know
if it is possible.
* No other serious idea sofar ...

  Any comment, any experience of moving large multiprojects
environments (think many dozens, if not hundreds of related projects)
with lots of different teams are welcomed.

  Thanks,

Guillaume
-- 
Jabber : [EMAIL PROTECTED]
Skype : Guillaume.Lederrey
Projects :
* http://rwanda.wordpress.com/
* http://rwandatech.wordpress.com/

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

Re: How to use different databases for tests and the actual application?

2007-10-26 Thread jimpo

Using application server -specified datasources is out of the question right
now unfortunately. Database connection details are configured inside the web
application.

It surprises me if Maven would not make it easy to use a different database
configuration for the tests and a different one for the created application.
This would basically make the dbUnit plugin pretty pointless, wouldn't it?
If you are creating a release of your application, you want the release to
point to a production db, but you still want the unit tests to be done
against a unit test db populated with dbUnit.

(not getting into whether such unit tests are really true unit tests...I
need them regardless of the term)

Arnaud Bailly wrote:

jimpo [EMAIL PROTECTED] writes:

I am using Maven2 to build my war packet. Base maven configuration is
created
with Appfuse http://appfuse.org/display/APF/Home.

When I do a mvn install (or mvn cargo:deploy), first a test phase
executes,
and then the final war is built and installed in the repository (or
deployed
to my app server).

I want to run the tests against a different db than which the final
package
uses. So far I have not figured out how to do this. Test phase uses the
same
database as the final application.

I figured out how to use profiles to switch between different databases.
I
can switch to test profile with, say, mvn test -Ptestdatabase. I could of
course use mvn test -Ptestdatabase to test and then separate command mvn
install -Dmaven.test.skip -Prealdatabase for creating the packet (and
skipping tests), but that's not very nice. I want to be able to issue one
command which does both phases, tests and packaging.

I am guessing maybe the solution would be something like activating
profile
X for the tests phase, and then activating a different profile Y for the
actual build. How could I accomplish this?

Hello,
I do not think possible right now to activate different profiles for
different phases in the same run. And I do not think this is
desirable. Maybe, if you are in a J2EE Container, you could use
different data sources parameters in test and production ? AFAIK, data
source configuration is independent of the applicaiont and configured
in the container, so you could use a test configuration, say with
hsqldb or derby in test, and another configuration in productoin. In
your webapp, data source reference will stay the same.

HTH
--
OQube software engineering \ génie logiciel
Arnaud Bailly, Dr.
\web http://www.oqube.com

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

--
View this message in context:
http://www.nabble.com/How-to-use-different-databases-for-tests-and-the-actual-application--tf4696771s177.html#a13426113
Sent from the Maven - Users mailing list archive at Nabble.com.

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

Re: release:prepare failure during scm-tag : Server certificate verification failed: issuer is not trusted

2007-10-26 Thread Jason Mihalick

Thanks for the help Rémy. Although your suggestion wasn't the nature of our
specific problem, I did end up getting this working after some more
searching on Google. What is bothering me, though, is that I still don't
know exactly why there was a problem in the first place. Here is what
ended up working for me.

Background:
My sources were initially checked out using using the subclipse plugin in
eclipse. After I checked them out, I executed the 'mvn release:prepare'
command, which was successful up to the point of creating the release tag as
I have mentioned previously.

Solution:
After reading your response and doing some more searching on Google, I found
http://64.233.167.104/search?q=cache:c-eapRRo1_gJ:docs.codehaus.org/display/MAVENUSER/MavenAndSourceforge+%2522issuer+is+not+trusted%2522+svnhl=enct=clnkcd=25gl=usclient=safari
this page on one of the codehaus wiki's. Their suggestion upon receiving
the Server certificate verification failed: issuer is not trusted was to
execute an 'svn log' command from the command line to force authentication
with the webserver. Sure enough, when I did that, the svn command line
client prompted me for my credentials and cached them. After that upon
executing an 'mvn release:prepare' maven was able to resume the release and
it was able to complete the tag operation.

It seems as though the credentials that were cached by subclipse when I did
the initial checkout of the sources were able to be used by maven when
committing my release to the trunk, but not when doing the tag. Why this is
the case, I don't know. Perhaps someone else can shed some light, but I've
had to file this as a UFO (Unexplained Funny Occurrence) and move on. sigh.

Thanks again for the help.

--
Jason

Rémy Sanlaville wrote:

Hi Jason,

Not sure, but if you can access to your svn repo with different URLs (
https://www.domain-ommitted.com and http://www.domain-ommitted.com for
instance) it's possible that you made a checkout via one URL
(http://www.domain-ommitted.com
for instance) and maven-release-plugin try with another URL specify in the
scm section of your pom (https://www.domain-ommitted.com for instance).

We had a such of problem with one of our project and maven-release-plugin
could also commit but not tag.

I am not sure for the explanation but maven-release-plugin uses the svn
client install in your computer.
For the commit, it uses all the information in your .svn
For the tag, it seems that it indicates the URL of the tags (specify in
the
scm section of your pom) but in your .svn the URL is different and the
certificate is linked only with the checkout URL.

HTH,

Rémy

--
View this message in context:
http://www.nabble.com/release%3Aprepare-failure-during-scm-tag-%3A---Server-certificate-verification-failed%3A-issuer-is-not-trusted-tf4678454s177.html#a13425936
Sent from the Maven - Users mailing list archive at Nabble.com.

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

Re: release:prepare failure during scm-tag : Server certificate verification failed: issuer is not trusted

On Fri, October 26, 2007 2:16 pm, Jason Mihalick wrote:

 It seems as though the credentials that were cached by subclipse when I
 did
 the initial checkout of the sources were able to be used by maven when
 committing my release to the trunk, but not when doing the tag.  Why this
 is
 the case, I don't know.

Subclipse (to my knowledge), uses a pure Java implementation of subversion
in order to work. As I understand it, this pure Java client[1] has its own
mechanism to handling credentials.

Maven's scm handling calls the svn binary directly, which then uses a
different mechanism for caching credentials. I suspect this is why your
behaviour in subclipse doesn't follow on from the behaviour of the svn
client.

[1] The pure Java svn client was written to solve the painful issue of
having to fiddle around with platform specific issues when trying to
execute the svn native binary.

Regards,
Graham
--



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

Re: dependencies outside maven

On Fri, October 26, 2007 2:20 pm, Guillaume Lederrey wrote:

   I'm working in a large organization, thinking of moving to maven. We
 have lots of projects, having lots of dependencies between them. For
 the moment, those projects are deployed in a central, proprietary
 repository. We have ant scripts taking care of downloading the jars
 needed by a project.

   We need to be able to transition to maven one project after another
 (we cant just stop working for one month ;-). So we need to be able to
 still refer to our old proprietary repository if we move a project
 to maven but not all its dependencies are managed by maven.

It is a pretty standard problem to have to support a bridged solution
while you move from one system to another.

We had to move off of a hacked together local repository hosted on a
windows share, to a proper maven repo hosted on a webserver.

Initially we started with an empty maven repo, and then manually imported
all the jars that were needed for each project from the existing
proprietry repo as we needed them.

What we did find is that the vast majority of jars being hosted in the old
repo were jars that were already available in the maven repos at
http://repo1.maven.org. In these cases, no import was done at all - we
just configured the pom files to use the correct versions of these
external jars, and let maven handle the downloads automatically.

There were a few jars left over that were no publically availalbe, and so
those jars were uploaded to our project-private in house repository.

At all times both the old ant based way, and the new maven way, worked for
those projects that had been converted. This way we eased off the old, and
eventually switched it off.

Regards,
Graham
--



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

Re: heap space error

2007-10-26 Thread Alonso Isidoro Roman

create MAVEN_OPTS system variable with :

-Xms512m -Xmx768m
 when 512 is initial memory and 768 is the max reachable..


 2007/10/26, Sonar, Nishant  [EMAIL PROTECTED]:
 
  Hi
 
 
 
  When I am runnin my maven pom I get the following error?
 
  Don't kno the root cause
 
 
 
  I ran the command
 
 
 
  'mvn -e clean install -Dmaven.test.skip=true'
 
 
 
  Does anybody can throw some light on this problem
 
 
 
  + Error stacktraces are turned on.
 
  [INFO] Scanning for projects...
 
  [INFO]
  
 
 
  [ERROR] FATAL ERROR
 
  [INFO]
  
 
  [INFO] Java heap space
 
  [INFO]
  
 
 
  [INFO] Trace
 
  java.lang.OutOfMemoryError: Java heap space
 
  [INFO]
  
 
  [INFO] Total time: 1 minute 59 seconds
 
  [INFO] Finished at: Fri Oct 26 06:37:28 EDT 2007
 
  [INFO] Final Memory: 4M/58M
 
  [INFO]
  
 
 
 
 
 
  Regards,
 
  Nishant
 
 


 --
 Alonso Isidoro Roman.




-- 
Alonso Isidoro Roman.

RE: heap space error

2007-10-26 Thread nick_stolwijk

It seems that Java ran out of heap space. Generally not a good sign. What Java 
version and Maven version are you running? What kind of project are you trying 
to build? Multimodule, special plugins, etc?

With regards,

Nick Stolwijk


-Original Message-
From: Sonar, Nishant [mailto:[EMAIL PROTECTED]
Sent: Fri 10/26/2007 12:57 PM
To: Maven Users List
Subject: heap space error
 
Hi 

 

When I am runnin my maven pom I get the following error?

 Don't kno the root cause 

 

I ran the command 

 

'mvn -e clean install -Dmaven.test.skip=true'

 

Does anybody can throw some light on this problem

 

+ Error stacktraces are turned on.

[INFO] Scanning for projects...

[INFO]


[ERROR] FATAL ERROR

[INFO]


[INFO] Java heap space

[INFO]


[INFO] Trace

java.lang.OutOfMemoryError: Java heap space

[INFO]


[INFO] Total time: 1 minute 59 seconds

[INFO] Finished at: Fri Oct 26 06:37:28 EDT 2007

[INFO] Final Memory: 4M/58M

[INFO]


 

 

Regards,

Nishant

Appearance company pom


Hi all,

I'm attempting to configure Continuum appearance in the apposite menu.

I fill the two  textBoxes with groupId and artifactId of my company pom
located in my private repository (under artifactory).
Then, after clicking save button, it says under POM Information:
Company POM 'org.pss:pss' doesn't exist. Create company POM

My question is:
where does continuum looks for company pom specified by specific groupId and
artifactId?

Thansk in advance.
Best regards
Raffaele
-- 
View this message in context: 
http://www.nabble.com/Appearance-company-pom-tf4697051.html#a13426369
Sent from the Continuum - Users mailing list archive at Nabble.com.

dependency:resolve and dependency:tree

2007-10-26 Thread Nigel Magnay

Hello

I have a war project (actually, a cargo uberwar project), which I want to
analyse using dependency:resolve / dependency:tree (and maybe even through
site reporting) in order to find dependency conflicts.

However - the dependency plugin does not show the jar files that are a part
of the dependent war files - it is cut off at the jar level.

Is it possible to configure it to descend the dependency tree into WAR
artifacts as well? Without this my dependency list looks fine, but I have
WAR files with differing versions in them...

Nigel

Re: Issues with recent update of maven-changes-plugin

2007-10-26 Thread Geraud Geraud

Thanks! I've forced the version to 2.0-beta2 and it worked.

--
Géraud

On 10/26/07, LAMY Olivier [EMAIL PROTECTED] wrote:
 Have you try with force the  maven-changes-plugin version to 2.0-beta-2 or 
 using a mvn version = 2.0.6 ?

 --
 Olivier

 -Message d'origine-
 De : Geraud Geraud [mailto:[EMAIL PROTECTED]
 Envoyé : vendredi 26 octobre 2007 12:32
 À : Maven Users List
 Objet : Issues with recent update of maven-changes-plugin

 Hi,

 it seems that the maven-metadata.xml at repo1.maven.org is incomplete
 : it doesn't refer to the version 2.0-beta-2, so I cannot build maven site on 
 my project (because I'm using Maven 2.0.5).

 The error is:
 [INFO] Ignoring available plugin update: 2.0-beta-3 as it requires Maven 
 version 2.0.6 [INFO] 
 
 [ERROR] BUILD ERROR
 [INFO] 
 
 [INFO] The plugin 'org.apache.maven.plugins:maven-changes-plugin' does not 
 exist or no valid version could be found


 Can anyone help?
 Thanks.
 --
 Géraud

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


 This e-mail, any attachments and the information contained therein (this 
 message) are confidential and intended solely for the use of the 
 addressee(s). If you have received this message in error please send it back 
 to the sender and delete it. Unauthorized publication, use, dissemination or 
 disclosure of this message, either in whole or in part is strictly prohibited.
 --
 Ce message électronique et tous les fichiers joints ainsi que  les 
 informations contenues dans ce message ( ci après le message ), sont 
 confidentiels et destinés exclusivement à l'usage de la  personne à laquelle 
 ils sont adressés. Si vous avez reçu ce message par erreur, merci  de le 
 renvoyer à son émetteur et de le détruire. Toutes diffusion, publication, 
 totale ou partielle ou divulgation sous quelque forme que se soit non 
 expressément autorisées de ce message, sont interdites.
 -


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



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

updatePolicy of artifact with packaging pom


Hi all,

I've noticed that if I modify then deploy a parent pom with packaging pom
(without changing its version), then If another person run mvn compile on a
child project of that parent (with updatePolicy set to always)) maven
doesn't see the modified parent pom.
How is it possible?
Perhaps the updatePolicy mechanism works only for pom with packaging jar?

In fact I noticed also that in the local repo, for artifact with packaging
pom isn't created the metadata file used (as I believe) by updatePolicy
mechanism to retrieve the new versions.

Thanks and best regards.
Raffaele
-- 
View this message in context: 
http://www.nabble.com/updatePolicy-of-artifact-with-packaging-pom-tf4697240s177.html#a13426932
Sent from the Maven - Users mailing list archive at Nabble.com.


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

Re: dependencies outside maven

On Fri, October 26, 2007 4:01 pm, Guillaume Lederrey wrote:

 The dependencies on standard jars is not really a problem for us. As
 you say, most of them are available already, and they tend not to
 change to often.

 Our problem comes from dependencies on internally produced jars. For
 example, we have a team working on a Swing Framework used by most of
 our projects, or many teams working on components / services reused by
 other internal projects. Those artifacts are deployed fairly often in
 our proprietary repository, and we have to be able to depend on them.

 It is not an option to build a dependency graph and migrate first the
 projects on which other projects depends. And it would be pretty heavy
 to manually update our maven repository to include new versions of our
 framework every time they do a release.

 For example, we need to be able to keep the framework deployed to our
 proprietary repo, but have dependencies to this framework from
 projects already migrating to maven.

You need to start at the bottom of your dependency tree, with those
dependencies that do not depend on other internal dependencies.

Get these bottom-most dependencies to the point where they are built by
and deployed by maven to an internal maven repository set up for your
project.

When you make a release of these bottom dependencies, go through the
formal maven release procedure (use the release plugin for this to make it
easy), and as a final step, copy the artifact from the maven repository
into your prorietry repo.

Eventually, over time, more of the code will start life in the maven repo,
until eventually you phase the proprietry repo out entirely. You can do
this as quickly or as slowly as you feel comfortable with.

Regards,
Graham
--



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

Re: dependency:resolve and dependency:tree

2007-10-26 Thread Nigel Magnay

.. and on a related note...

When I do dependency:tree on a project that contains

dependency
groupIdorg.hibernate/groupId
artifactIdhibernate/artifactId
version3.2.4.ga/version
typejar/type
scopecompile/scope
/dependency

In the hibernate pom in my repository, it says
...
   dependency
groupIdcommons-collections/groupId
artifactIdcommons-collections/artifactId
version2.1.1/version
   /dependency
...
Why does dependency:tree show it as 3.1 ?!?!

 org.hibernate:hibernate:jar:3.2.4.ga:compile
[INFO]   net.sf.ehcache:ehcache:jar:1.2.3:compile
[INFO]  commons-logging:commons-logging:jar:1.1:compile
[INFO]  asm:asm-attrs:jar:1.5.3:compile
[INFO]  antlr:antlr:jar:2.7.6:compile
[INFO]  cglib:cglib:jar:2.1_3:compile
[INFO]  asm:asm:jar:1.5.3:compile
[INFO]  commons-collections:commons-collections:jar:3.1:compile

Is this also the reason why my dependency convergence report looks OK, when
really there's a mismatch ?



On 26/10/2007, Nigel Magnay [EMAIL PROTECTED] wrote:

 Hello

 I have a war project (actually, a cargo uberwar project), which I want to
 analyse using dependency:resolve / dependency:tree (and maybe even through
 site reporting) in order to find dependency conflicts.

 However - the dependency plugin does not show the jar files that are a
 part of the dependent war files - it is cut off at the jar level.

 Is it possible to configure it to descend the dependency tree into WAR
 artifacts as well? Without this my dependency list looks fine, but I have
 WAR files with differing versions in them...

 Nigel

Re: release:prepare failure during scm-tag : Server certificate verification failed: issuer is not trusted

2007-10-26 Thread Jason Mihalick

Thanks for the info Graham. That does make some sense. However, do you have
any ideas why the maven release plugin would be able to execute the commit
of the release POMs to the trunk prior to tagging? I can't figure that one
out, unless I've somehow misinterpreted the sequence of events that lead up
to this problem.

Best regards,
Jason

Graham Leggett wrote:

On Fri, October 26, 2007 2:16 pm, Jason Mihalick wrote:

Subclipse (to my knowledge), uses a pure Java implementation of subversion
in order to work. As I understand it, this pure Java client[1] has its own
mechanism to handling credentials.

Maven's scm handling calls the svn binary directly, which then uses a
different mechanism for caching credentials. I suspect this is why your
behaviour in subclipse doesn't follow on from the behaviour of the svn
client.

[1] The pure Java svn client was written to solve the painful issue of
having to fiddle around with platform specific issues when trying to
execute the svn native binary.

Regards,
Graham
--

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

--
View this message in context:
http://www.nabble.com/release%3Aprepare-failure-during-scm-tag-%3A---Server-certificate-verification-failed%3A-issuer-is-not-trusted-tf4678454s177.html#a13428128
Sent from the Maven - Users mailing list archive at Nabble.com.

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

RE: Issues with recent update of maven-changes-plugin

2007-10-26 Thread Jörg Schaible

LAMY Olivier wrote:
 Have you try with force the  maven-changes-plugin version to
 2.0-beta-2 or using a mvn version = 2.0.6 ?

Gosh! What's this? We have locked the version in the pluginManagement and 
nevertheless the plugin is updated while making the release:

= % =
$ mvn release:perform
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'release'.
[INFO] 

[INFO] Building CS eFile Master Project
[INFO]task-segment: [release:perform] (aggregator-style)
[INFO] 

[INFO] [release:perform]
[INFO] Checking out the project to perform the release ...
[INFO] Executing: svn --non-interactive checkout 
http://websvn/svn/essvn/development/projects/XXX/pom/tags/v_1 checkout
[INFO] Working directory: D:\work\projects\credit-suisse\eFile\pom\target
[INFO] Executing goals 'deploy site-deploy'...
[INFO] Executing: mvn deploy site-deploy --no-plugin-updates -P 
elsag,msvc,elsag,msvc -DperformRelease=true
[INFO] Scanning for projects...
[INFO] 

[INFO] Building CS eFile Master Project
[INFO]task-segment: [deploy, site-deploy]
[INFO] 

[INFO] [site:attach-descriptor]
[INFO] Preparing source:jar
[WARNING] Removing: jar from forked lifecycle, to prevent recursive 
invocation.
[INFO] No goals needed for project - skipping
[INFO] [source:jar {execution: attach-sources}]
[INFO] Preparing javadoc:jar
[WARNING] Removing: jar from forked lifecycle, to prevent recursive 
invocation.
[WARNING] Removing: jar from forked lifecycle, to prevent recursive 
invocation.
[INFO] No goals needed for project - skipping
[INFO] [javadoc:jar {execution: attach-javadocs}]
[INFO] Not executing Javadoc as the project is not a Java classpath-capable 
package
[INFO] [install:install]
[INFO] Installing D:\work\projects\XXX\pom\target\checkout\pom.xml to 
d:\repository\m2\com\elsagsolutions\projects\XXX\master\1\master-1.pom
[INFO] [deploy:deploy]
altDeploymentRepository = null
Uploading: 
file:/es3.elsag.de/maven/repo-m2/com/elsagsolutions/projects/XXX/master/1/master-1.pom
4/7K
7/7K
7K uploaded
[INFO] Retrieving previous metadata from elsag-release
[INFO] Uploading repository metadata for: 'artifact 
com.elsagsolutions.projects.cs.eFile:master'
[INFO] artifact org.apache.maven.plugins:maven-changes-plugin: checking for 
updates from central
[INFO] artifact org.apache.maven.plugins:maven-changes-plugin: checking for 
updates from elsag-plugin-release
Downloading: 
http://es3.elsag.de:8234/org/apache/maven/plugins/maven-changes-plugin/2.0-beta-3/maven-changes-plugin-2.0-beta-3.pom
4/11K
8/11K
11/11K
11K downloaded
[INFO] Ignoring available plugin update: 2.0-beta-3 as it requires Maven 
version 2.0.6
[INFO] 

[ERROR] BUILD ERROR
[INFO] 

[INFO] The plugin 'org.apache.maven.plugins:maven-changes-plugin' does not 
exist or no valid version could be found
[INFO] 

[INFO] For more information, run Maven with the -e switch
[INFO] 

[INFO] Total time: 15 seconds
[INFO] Finished at: Fri Oct 26 15:58:08 CEST 2007
[INFO] Final Memory: 9M/17M
[INFO] 

[INFO] 
[ERROR] BUILD ERROR
[INFO] 
[INFO] Maven execution failed, exit code: '1'

[INFO] 
[INFO] For more information, run Maven with the -e switch
[INFO] 
[INFO] Total time: 25 seconds
[INFO] Finished at: Fri Oct 26 15:58:08 CEST 2007
[INFO] Final Memory: 5M/10M
[INFO] 
= % =

This is a completely QA nightmare!!! 

- Jörg

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

Re: Appearance company pom

2007-10-26 Thread olivier lamy

Hi,
Argh :-).
One can load an issue ?
And this could be fix for 1.1
Thanks,
--
Olivier

2007/10/26, Stephane Nicoll [EMAIL PROTECTED]:

 Same here. This does not work since the early days of continuum 1.1.
 I'm actually surprised that you guys never detected it

 (use a pom that is *not* on central)

 Stéphane

 On 10/26/07, Raffaele [EMAIL PROTECTED] wrote:
 
  But in my local repo there is the company pom that I have specified in
 the
  Continuum web UI...
 
  My company pom has gropudId=org.pss and artifactId=pss and so I
 specify
  those values in the corresponding textBoxes then click on save button...
 
  regards
  Raffaele
 
 
  Wendy Smoak-3 wrote:
  
   On 10/26/07, Raffaele [EMAIL PROTECTED] wrote:
  
   My question is:
   where does continuum looks for company pom specified by specific
 groupId
   and
   artifactId?
  
   Last time I fought with appearance it would only look in
   ~/.m2/repository.  Unless something has changed, it won't go look in a
   remote repo for the pom.
  
   --
   Wendy
  
  
 
  --
  View this message in context:
 http://www.nabble.com/Appearance-company-pom-tf4697051.html#a13427446
  Sent from the Continuum - Users mailing list archive at Nabble.com.
 
 


 --
 Large Systems Suck: This rule is 100% transitive. If you build one,
 you suck -- S.Yegge

Re: dependencies outside maven

Thank you for your answer ! There is a few points still unclear to me
: see below

On 26/10/2007, Graham Leggett [EMAIL PROTECTED] wrote:
 On Fri, October 26, 2007 2:20 pm, Guillaume Lederrey wrote:

I'm working in a large organization, thinking of moving to maven. We
  have lots of projects, having lots of dependencies between them. For
  the moment, those projects are deployed in a central, proprietary
  repository. We have ant scripts taking care of downloading the jars
  needed by a project.
 
We need to be able to transition to maven one project after another
  (we cant just stop working for one month ;-). So we need to be able to
  still refer to our old proprietary repository if we move a project
  to maven but not all its dependencies are managed by maven.

 It is a pretty standard problem to have to support a bridged solution
 while you move from one system to another.

 We had to move off of a hacked together local repository hosted on a
 windows share, to a proper maven repo hosted on a webserver.

 Initially we started with an empty maven repo, and then manually imported
 all the jars that were needed for each project from the existing
 proprietry repo as we needed them.

 What we did find is that the vast majority of jars being hosted in the old
 repo were jars that were already available in the maven repos at
 http://repo1.maven.org. In these cases, no import was done at all - we
 just configured the pom files to use the correct versions of these
 external jars, and let maven handle the downloads automatically.

The dependencies on standard jars is not really a problem for us. As
you say, most of them are available already, and they tend not to
change to often.

Our problem comes from dependencies on internally produced jars. For
example, we have a team working on a Swing Framework used by most of
our projects, or many teams working on components / services reused by
other internal projects. Those artifacts are deployed fairly often in
our proprietary repository, and we have to be able to depend on them.

It is not an option to build a dependency graph and migrate first the
projects on which other projects depends. And it would be pretty heavy
to manually update our maven repository to include new versions of our
framework every time they do a release.

For example, we need to be able to keep the framework deployed to our
proprietary repo, but have dependencies to this framework from
projects already migrating to maven.

Does it make sense ?


 There were a few jars left over that were no publically availalbe, and so
 those jars were uploaded to our project-private in house repository.

 At all times both the old ant based way, and the new maven way, worked for
 those projects that had been converted. This way we eased off the old, and
 eventually switched it off.

 Regards,
 Graham
 --



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




-- 
Jabber : [EMAIL PROTECTED]
Skype : Guillaume.Lederrey
Projects :
* http://rwanda.wordpress.com/
* http://rwandatech.wordpress.com/

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

Re: Appearance company pom


But in my local repo there is the company pom that I have specified in the
Continuum web UI...

My company pom has gropudId=org.pss and artifactId=pss and so I specify
those values in the corresponding textBoxes then click on save button...

regards
Raffaele


Wendy Smoak-3 wrote:
 
 On 10/26/07, Raffaele [EMAIL PROTECTED] wrote:
 
 My question is:
 where does continuum looks for company pom specified by specific groupId
 and
 artifactId?
 
 Last time I fought with appearance it would only look in
 ~/.m2/repository.  Unless something has changed, it won't go look in a
 remote repo for the pom.
 
 -- 
 Wendy
 
 

-- 
View this message in context: 
http://www.nabble.com/Appearance-company-pom-tf4697051.html#a13427446
Sent from the Continuum - Users mailing list archive at Nabble.com.

Re: Appearance company pom

2007-10-26 Thread Stephane Nicoll

Same here. This does not work since the early days of continuum 1.1.
I'm actually surprised that you guys never detected it

(use a pom that is *not* on central)

Stéphane

On 10/26/07, Raffaele [EMAIL PROTECTED] wrote:

 But in my local repo there is the company pom that I have specified in the
 Continuum web UI...

 My company pom has gropudId=org.pss and artifactId=pss and so I specify
 those values in the corresponding textBoxes then click on save button...

 regards
 Raffaele


 Wendy Smoak-3 wrote:
 
  On 10/26/07, Raffaele [EMAIL PROTECTED] wrote:
 
  My question is:
  where does continuum looks for company pom specified by specific groupId
  and
  artifactId?
 
  Last time I fought with appearance it would only look in
  ~/.m2/repository.  Unless something has changed, it won't go look in a
  remote repo for the pom.
 
  --
  Wendy
 
 

 --
 View this message in context: 
 http://www.nabble.com/Appearance-company-pom-tf4697051.html#a13427446
 Sent from the Continuum - Users mailing list archive at Nabble.com.




-- 
Large Systems Suck: This rule is 100% transitive. If you build one,
you suck -- S.Yegge

Re: dependencies outside maven

On 26/10/2007, Graham Leggett [EMAIL PROTECTED] wrote:
 On Fri, October 26, 2007 4:01 pm, Guillaume Lederrey wrote:

  The dependencies on standard jars is not really a problem for us. As
  you say, most of them are available already, and they tend not to
  change to often.
 
  Our problem comes from dependencies on internally produced jars. For
  example, we have a team working on a Swing Framework used by most of
  our projects, or many teams working on components / services reused by
  other internal projects. Those artifacts are deployed fairly often in
  our proprietary repository, and we have to be able to depend on them.
 
  It is not an option to build a dependency graph and migrate first the
  projects on which other projects depends. And it would be pretty heavy
  to manually update our maven repository to include new versions of our
  framework every time they do a release.
 
  For example, we need to be able to keep the framework deployed to our
  proprietary repo, but have dependencies to this framework from
  projects already migrating to maven.

 You need to start at the bottom of your dependency tree, with those
 dependencies that do not depend on other internal dependencies.

  That's our main problem !

  For organizational / political reasons, the bottom of our
dependency tree will not migrate anytime soon ... that's why we need
some way to depend on projects NOT in the maven repository ...

  I know, we're going to have a lot of fun !

 Get these bottom-most dependencies to the point where they are built by
 and deployed by maven to an internal maven repository set up for your
 project.

 When you make a release of these bottom dependencies, go through the
 formal maven release procedure (use the release plugin for this to make it
 easy), and as a final step, copy the artifact from the maven repository
 into your prorietry repo.

 Eventually, over time, more of the code will start life in the maven repo,
 until eventually you phase the proprietry repo out entirely. You can do
 this as quickly or as slowly as you feel comfortable with.

 Regards,
 Graham
 --



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




-- 
Jabber : [EMAIL PROTECTED]
Skype : Guillaume.Lederrey
Projects :
* http://rwanda.wordpress.com/
* http://rwandatech.wordpress.com/

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

RE: Issues with recent update of maven-changes-plugin

2007-10-26 Thread LAMY Olivier

Looks to be only a workaround.
It's not normal to not have 2.0-beta-2 in the metadata here :
http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-changes-plugin/maven-metadata.xml

--
Olivier  

-Message d'origine-
De : Geraud Geraud [mailto:[EMAIL PROTECTED] 
Envoyé : vendredi 26 octobre 2007 15:39
À : Maven Users List
Objet : Re: Issues with recent update of maven-changes-plugin

Thanks! I've forced the version to 2.0-beta2 and it worked.

--
Géraud

On 10/26/07, LAMY Olivier [EMAIL PROTECTED] wrote:
 Have you try with force the  maven-changes-plugin version to 2.0-beta-2 or 
 using a mvn version = 2.0.6 ?

 --
 Olivier

 -Message d'origine-
 De : Geraud Geraud [mailto:[EMAIL PROTECTED] Envoyé : vendredi 26 
 octobre 2007 12:32 À : Maven Users List Objet : Issues with recent 
 update of maven-changes-plugin

 Hi,

 it seems that the maven-metadata.xml at repo1.maven.org is incomplete
 : it doesn't refer to the version 2.0-beta-2, so I cannot build maven site on 
 my project (because I'm using Maven 2.0.5).

 The error is:
 [INFO] Ignoring available plugin update: 2.0-beta-3 as it requires 
 Maven version 2.0.6 [INFO] 
 --
 --
 [ERROR] BUILD ERROR
 [INFO] 
 --
 -- [INFO] The plugin 'org.apache.maven.plugins:maven-changes-plugin' 
 does not exist or no valid version could be found


 Can anyone help?
 Thanks.
 --
 Géraud

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


 This e-mail, any attachments and the information contained therein (this 
 message) are confidential and intended solely for the use of the 
 addressee(s). If you have received this message in error please send it back 
 to the sender and delete it. Unauthorized publication, use, dissemination or 
 disclosure of this message, either in whole or in part is strictly prohibited.
 --
 
 Ce message électronique et tous les fichiers joints ainsi que  les 
 informations contenues dans ce message ( ci après le message ), sont 
 confidentiels et destinés exclusivement à l'usage de la  personne à laquelle 
 ils sont adressés. Si vous avez reçu ce message par erreur, merci  de le 
 renvoyer à son émetteur et de le détruire. Toutes diffusion, publication, 
 totale ou partielle ou divulgation sous quelque forme que se soit non 
 expressément autorisées de ce message, sont interdites.
 --
 ---


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



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

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

continuum ERROR wrapper JVM appears hung: Timed out waiting for signal from JVM.

2007-10-26 Thread VanIngen, Erik (ESTG)

Hi Continuum, 

Working with Continuum 1.1-beta-3 and received this message. Did some
research on the internet but did not find a proper solution. Any ideas?

continuum ERROR wrapper JVM appears hung: Timed out waiting for signal from
JVM.

*
I already did this:
During the build of fenix-web, the process ran probably into low memory and
was lost. I extended the memory from 384 to 500Mb and after the problem was
solved. The configuration file can be found here:
\continuum-1.1-beta-3\bin\windows-x86-3\ wrapper.conf
*


Kind Regards,
Erik

Re: dependencies outside maven

On Fri, October 26, 2007 4:47 pm, Guillaume Lederrey wrote:

   That's our main problem !

   For organizational / political reasons, the bottom of our
 dependency tree will not migrate anytime soon ... that's why we need
 some way to depend on projects NOT in the maven repository ...

In that case, you will need to deploy these bottom packages into your
maven repository, and set up the poms for them by hand.

Basically, for maven to work, it needs dependencies in a maven repo. Maven
doesn't care how those dependencies got created (old build system, new
build system, doesn't matter), only that the dependencies are where maven
expects to find them in the correct directory structure on the maven repo.

   I know, we're going to have a lot of fun !

Keep things small and simple, and do things one step at a time.

We finished the migration of a project that combined EJB elements with
Eclipse RCP, and beginning to end the full migration process took a full
year. The rewards are worth it though: We need to release code at short
notice, and this process is now a non event for us, typically completed
within 30 minutes.

Regards,
Graham
--



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

Re: dependencies outside maven

You can try to use scopesystem/scope bug this is generally not
encouraged as it does not work as you might expect in all situations.
This would allow you to pull your artifacts from your current system,
put them in a /lib folder, and use them as part of your current Maven
build.

However, I think this is a bad idea -- system scope is not a long-term
solution, and not a great short-term solution either. Instead I would
build a little shell script that would analyze your pom, go out to
your proprietary repo and download the necessary files and then use
mvn install:install-file -DgeneratePom=true -DcreateChecksum=true
... to install each one into your local Maven repo cache.

Ideally once you got things working on your local environment, you
would use mvn deploy to deploy your code to a new Maven (corporate)
repo that you will set up that will function as your new artifact
repository. I would also write a script to run mvn
deploy:deploy-file similar to the mvn install script mentioned
above, so you will migrate not only the current app you're working on
but also all of its related support libraries etc.

Wayne

On 10/26/07, Guillaume Lederrey [EMAIL PROTECTED] wrote:
 On 26/10/2007, Graham Leggett [EMAIL PROTECTED] wrote:
  On Fri, October 26, 2007 4:01 pm, Guillaume Lederrey wrote:
 
   The dependencies on standard jars is not really a problem for us. As
   you say, most of them are available already, and they tend not to
   change to often.
  
   Our problem comes from dependencies on internally produced jars. For
   example, we have a team working on a Swing Framework used by most of
   our projects, or many teams working on components / services reused by
   other internal projects. Those artifacts are deployed fairly often in
   our proprietary repository, and we have to be able to depend on them.
  
   It is not an option to build a dependency graph and migrate first the
   projects on which other projects depends. And it would be pretty heavy
   to manually update our maven repository to include new versions of our
   framework every time they do a release.
  
   For example, we need to be able to keep the framework deployed to our
   proprietary repo, but have dependencies to this framework from
   projects already migrating to maven.
 
  You need to start at the bottom of your dependency tree, with those
  dependencies that do not depend on other internal dependencies.

  That's our main problem !

  For organizational / political reasons, the bottom of our
 dependency tree will not migrate anytime soon ... that's why we need
 some way to depend on projects NOT in the maven repository ...

  I know, we're going to have a lot of fun !

  Get these bottom-most dependencies to the point where they are built by
  and deployed by maven to an internal maven repository set up for your
  project.
 
  When you make a release of these bottom dependencies, go through the
  formal maven release procedure (use the release plugin for this to make it
  easy), and as a final step, copy the artifact from the maven repository
  into your prorietry repo.
 
  Eventually, over time, more of the code will start life in the maven repo,
  until eventually you phase the proprietry repo out entirely. You can do
  this as quickly or as slowly as you feel comfortable with.
 
  Regards,
  Graham
  --
 
 
 
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 


 --
 Jabber : [EMAIL PROTECTED]
 Skype : Guillaume.Lederrey
 Projects :
 * http://rwanda.wordpress.com/
 * http://rwandatech.wordpress.com/

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



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

Re: Debugging failed junit-test

2007-10-26 Thread Jan Torben Heuer

Tim Kettler wrote:


 They are simply not part of the artifact maven creates for module2. The
 artifact maven creates contains just the production code (classes and
 resources from 'src/main/*') as no one seriously wants to have their
 unit tests packaged alongsite the final deliverable of the project.
Ok, that make sense - although a test-compile should - in my eyes - compile
all classes to another destination.

 If you have shared testing code between two projects, just create a
 third module containig this shared code and declare it as a dependency
 in the two other modules with scopetest/scope or follow the guide
 Wanyne pointed you to and create a test-jar of the testing code in
 module2 and reference that with test scope.

Ok, if it is a library that should provide Mock Objects and
example-request-documents.
Creating a second artifact only for the MockObjects and request-examples is
a bit annoying.

But it seems to be the only soloution, right?

Jan


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

Properties files exclude from jar artifact

2007-10-26 Thread Saloucious


Hi,

Acutally, i'm working on a migration from Ant to Maven.
The old Ant script creates for each project a  jar and  copy properties
files in a deploy dir.
So these properties file are not embeded in jar.

Now i'm on Maven, 
If I excludes files from jar, they will not be in repository
I don't find the way to be able to not embed properties file from jar and
install them in repo.
-- 
View this message in context: 
http://www.nabble.com/Properties-files-exclude-from-jar-artifact-tf4698085s177.html#a13429857
Sent from the Maven - Users mailing list archive at Nabble.com.


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

Maven checkstyle plugin, multimodule conf problem

2007-10-26 Thread vetalok


Hello experts!
I have the following structure:
whizbang
|-- pom.xml
|-- a
|   `-- pom.xml
|   `-- target/site/checkstyle.html
|-- b
|   `-- pom.xml
|   `-- target/site/checkstyle.html
These checkstyle.htmls were created by running mvn checkstyle:checkstyle
comand in whizbang directory.
How can I autamatically combine all these  checkstyle.htmls into single
checkstyle.html?
Thanks.

-- 
View this message in context: 
http://www.nabble.com/Maven-checkstyle-plugin%2C-multimodule-conf-problem-tf4697789s177.html#a13428818
Sent from the Maven - Users mailing list archive at Nabble.com.


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

Re: Properties files exclude from jar artifact

You could make another artifact (jar) that consists only of properties
files that are jar'ed together and deploy it into your repo.

Wayne

On 10/26/07, Saloucious [EMAIL PROTECTED] wrote:

 Hi,

 Acutally, i'm working on a migration from Ant to Maven.
 The old Ant script creates for each project a  jar and  copy properties
 files in a deploy dir.
 So these properties file are not embeded in jar.

 Now i'm on Maven,
 If I excludes files from jar, they will not be in repository
 I don't find the way to be able to not embed properties file from jar and
 install them in repo.
 --
 View this message in context: 
 http://www.nabble.com/Properties-files-exclude-from-jar-artifact-tf4698085s177.html#a13429857
 Sent from the Maven - Users mailing list archive at Nabble.com.


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



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

Re: How can I get the path for a root pom.xml's basedir in a multimodule project with pom inheritance

2007-10-26 Thread clamb


OK, i've been fighting this battle for a few days now and have a fairly ugly
solution.

in every pom.xml define a common root property:

  properties
rootPOM${basedir}/..//rootPOM
  /properties

Ensure that you have enough ../ to reference the rootPOM directory.

Everywhere you need to refer to this super root directory use ${rootPOM}.



Matthew McCullough wrote:
 
 My far-from-modern CM group requires that we check in the binary artifacts
 for our 3ps, and depend on them from a VOB checked out of ClearCase.  So
 our repo, as is now supported in Maven 2, is a file://../../3pvob type
 of path rather than an HTTP path.
 
 Let me know if you have any more ideas on this.  And thanks again all.
 
 -Matthew
 

-- 
View this message in context: 
http://www.nabble.com/How-can-I-get-the-path-for-a-root-pom.xml%27s-basedir-in-a-multimodule-project-with-pom-inheritance-tf4577123s177.html#a13431339
Sent from the Maven - Users mailing list archive at Nabble.com.


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

Coberatura with integration tests

2007-10-26 Thread Morris Jones


I'm beginning to think this is impossible in Maven2:

Suppose I want to use Cargo, Selenium, and Cobertura to get a coverage 
number in a web application, but I don't want the process to interfere 
with a Continuum build on a headless Linux box.


I'm so tangled up in the mass of configuration files and dependencies, I 
can't quite figure out how to begin.


Is this just something that I'm going to have to do manually and ignore 
Maven?


Mojo
--
Morris Jones
Monrovia, CA
http://www.whiteoaks.com
Old Town Astronomers: http://www.otastro.org

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

Re: Gentoo Linux init.d script?

2007-10-26 Thread Hilco Wijbenga

I've created an init script for Gentoo that seems to work.

#!/sbin/runscript

depend() {
need net localmount
after bootmisc
}

start() {
ebegin Starting Continuum
start-stop-daemon --background --make-pidfile --pidfile
/var/run/continuum.pid --chuid apache --name java --start --exec
/YOUR_DIR/continuum/bin/plexus.sh
eend $?
}

stop() {
ebegin Stopping Continuum
start-stop-daemon --stop --pidfile /var/run/continuum.pid
eend $?
}

Give it a try and let me know if it works.

[DISCLAIMER] I'm by no means a Gentoo expert, just a fairly
experienced user. This seems to work, I'm not saying this is the best
way to do it.

Re: How does maven resolve plugin dependencies

2007-10-26 Thread alexworden

Hi,

The odd thing is that this was working just fine last week. I didn't change
a thing, and now it's broken. It's not related to being behind a firewall
since I'm trying it from home, where I don't have a firewall - and it was
working here last week.

What ports does maven try to connect to the repository on anyway?

Where are the repositories configured?

If I have a local repository configured, will maven also try to look in the
default repositories?

Again - if anyone can explain what maven is doing in order to look-up the
plugin location, that would be helpful.

Thanks,

Alex

alexworden wrote:

Wayne Fay wrote:

The plugin 'org.apache.maven.plugins:maven-eclipse-plugin' does not
exist or
no valid version could be found

There are several reasons why this will happen. In short, Maven is
unable to find the plugin. For new users, this generally means that
you're behind some kind of Internet proxy and simply have failed to
configure it in your settings.xml as is required.

From what I gather, maven should look in:
http://repo1.maven.org/maven2/eclipse/ but when I browse there, I don't
find
any versions available. Is there something wrong with the maven
repository
right now? very mysterious...

This is incorrect. The correct url is:
http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-eclipse-plugin/

Wayne

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

--
View this message in context:
http://www.nabble.com/How-does-maven-resolve-plugin-dependencies-tf4694740s177.html#a13432043
Sent from the Maven - Users mailing list archive at Nabble.com.

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

Re: Building Eclipse plugins with Maven 2

2007-10-26 Thread Carlos Sanchez

you can see an example of an eclipse plugin build with maven at
http://q4e.googlecode.com/svn/branches/built-with-maven/embedder/

On 10/26/07, Sebastien ARBOGAST [EMAIL PROTECTED] wrote:
 I finally found some lead to progress.
 I managed to build and install the original version of the mojos.
 Then I found something: it's all a problem of dependency versions. In my
 source-plugin module manifest dependencies, I did not specify any version
 for the plugins on which I depend, which caused the modified pom to
 reference 1.0 version by default.
 Now I added a version for the plugins that are in my workspace
 (source-plugin et binary-plugin) and it's looking for the right versions.
 But I still have a problem for plugins that are supposed to be provided by
 Eclipse itself. It seems that they are not deployed to my local repository
 or it's looking in the wrong directories:

 1) com.mycompany.eclipse:org.eclipse.ui.ide:pom:1.0
   Path to dependency:
 1)
 com.mycompany.eclipse:com.mycompany.framework.eclipse.rcp:source-pl
 ugin:1.0-SNAPSHOT
 2) com.mycompany.eclipse:org.eclipse.ui.ide:pom:1.0

 Obviously some bits and pieces are missing.

 2007/10/26, Sebastien ARBOGAST [EMAIL PROTECTED] :
 
  OK, I really need this to work because I'm fed up with ant maintenance and
  manual dependency management.
 
  I've tried to start all over again. I think the problem might have come
  from the fact that I was not using the original version of the mojos
  described by the author of the article, but one that I found on m2eclipse
  repository. Do I downloaded the original version linked in the article, but
  when I tried to build it, it failed because it doesn't find maven-pst parent
  project. Does anyone know where I can fin that project?
 
  2007/10/23, Sebastien ARBOGAST [EMAIL PROTECTED] :
  
   I checked out the last version I could find in the m2eclipse project: 
   http://svn.codehaus.org/m2eclipse/maven-pst
  
  
   That's the one I'm using with a few modifications to the POM in order to
   build against Maven 2.0.7 and Eclipse 3.3.1
  
   Now here are the error messages that I get:
  
   [INFO]
   
   [ERROR] BUILD ERROR
   [INFO]
   
   [INFO] Failed to resolve artifact.
  
   Missing:
   --
   1) com.myapp.eclipse:org.springframework.spring:pom:1.0
 Path to dependency:
   1) com.myapp.eclipse:com.myapp.framework.eclipse.rcp:source-pl
   ugin:1.0-SNAPSHOT
   2) com.myapp.eclipse:org.springframework.spring:pom:1.0
  
   2) com.myapp.eclipse:org.eclipse.core.databinding:pom:1.0
 Path to dependency:
   1) com.myapp.eclipse:com.myapp.framework.eclipse.rcp:source-pl
   ugin:1.0-SNAPSHOT
   2) com.myapp.eclipse:org.eclipse.core.databinding:pom:1.0
  
   3) com.myapp.eclipse:org.apache.log4j:pom:1.0
 Path to dependency:
   1) com.myapp.eclipse:com.myapp.framework.eclipse.rcp:source-pl
   ugin:1.0-SNAPSHOT
   2) com.myapp.eclipse:org.apache.log4j:pom:1.0
  
   4) com.myapp.eclipse:com.myapp.framework.common:pom:1.0-SNAPSHOT
 Path to dependency:
   1) com.myapp.eclipse:com.myapp.framework.eclipse.rcp:source-pl
   ugin:1.0-SNAPSHOT
   2) com.myapp.eclipse:com.myapp.framework.common:pom:1.0-SNAPSH
   OT
  
   5) com.myapp.eclipse:org.eclipse.ui:jar:1.0
  
 Try downloading the file manually from the project website.
  
 Then, install it using the command:
 mvn install:install-file -DgroupId=com.myapp.eclipse-DartifactId=org
   .eclipse.ui \
 -Dversion=1.0 -Dpackaging=jar -Dfile=/path/to/file
  
 Path to dependency:
   1) com.myapp.eclipse:com.myapp.framework.eclipse.rcp:source-pl
   ugin:1.0-SNAPSHOT
   2) com.myapp.eclipse:org.eclipse.ui:jar:1.0
  
   6) com.myapp.eclipse:org.eclipse.core.runtime:jar:1.0
  
 Try downloading the file manually from the project website.
  
 Then, install it using the command:
 mvn install:install-file -DgroupId=com.myapp.eclipse-DartifactId=org
   .eclipse.core.runtime \
 -Dversion=1.0 -Dpackaging=jar -Dfile=/path/to/file
  
 Path to dependency:
   1) com.myapp.eclipse:com.myapp.framework.eclipse.rcp:source-pl
   ugin:1.0-SNAPSHOT
   2) com.myapp.eclipse:org.eclipse.core.runtime:jar:1.0
  
   7) com.myapp.eclipse:org.eclipse.jface.databinding:pom:1.0
 Path to dependency:
   1) com.myapp.eclipse:com.myapp.framework.eclipse.rcp:source-pl
   ugin:1.0-SNAPSHOT
   2) com.myapp.eclipse:org.eclipse.jface.databinding:pom:1.0
  
   8) com.myapp.eclipse:com.myapp.security.crypto.smartcard:pom:1.0-SNAPS
   HOT
 Path to dependency:
   1) com.myapp.eclipse:com.myapp.framework.eclipse.rcp:source-pl
   ugin:1.0-SNAPSHOT
   2) com.myapp.eclipse:com.myapp.security.crypto.smartcard:pom:1
   .0-SNAPSHOT
  
   9)

Re: How does maven resolve plugin dependencies

Its simply not that straightforward as there are many things you can
configure in various places etc. By default, Maven looks in the
Central repo, but you can override this or set up mirrors etc.

Try mvn -U -X eclipse:eclipse and if it still fails, copy and paste
the log into pastebin.com and send the link here.

Wayne

On 10/26/07, alexworden [EMAIL PROTECTED] wrote:

Hi,

What ports does maven try to connect to the repository on anyway?

Where are the repositories configured?

If I have a local repository configured, will maven also try to look in the
default repositories?

Again - if anyone can explain what maven is doing in order to look-up the
plugin location, that would be helpful.

Thanks,

Alex

alexworden wrote:

Wayne Fay wrote:

The plugin 'org.apache.maven.plugins:maven-eclipse-plugin' does not
exist or
no valid version could be found

This is incorrect. The correct url is:
http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-eclipse-plugin/

Wayne

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

--
View this message in context:
http://www.nabble.com/How-does-maven-resolve-plugin-dependencies-tf4694740s177.html#a13432043
Sent from the Maven - Users mailing list archive at Nabble.com.

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

Re: How does maven resolve plugin dependencies

2007-10-26 Thread alexworden

Thanks for your suggestions Wayne. I found a way to fix the issue.

I searched in my local repository under org.apache.maven.plugins... and
found that it did not contain a version directory (that should contain the
jars etc) - just a couple of xml files describing the artifact etc.

I deleted the directory and behold! It worked!

I didn't delete the jars. Maven must have done something with them??

I still think it would be very useful if someone could deterministically
document what on earth maven is doing.

Wayne Fay wrote:

Its simply not that straightforward as there are many things you can
configure in various places etc. By default, Maven looks in the
Central repo, but you can override this or set up mirrors etc.

Try mvn -U -X eclipse:eclipse and if it still fails, copy and paste
the log into pastebin.com and send the link here.

Wayne

On 10/26/07, alexworden [EMAIL PROTECTED] wrote:

Hi,

The odd thing is that this was working just fine last week. I didn't
change
a thing, and now it's broken. It's not related to being behind a firewall
since I'm trying it from home, where I don't have a firewall - and it was
working here last week.

What ports does maven try to connect to the repository on anyway?

Where are the repositories configured?

If I have a local repository configured, will maven also try to look in
the
default repositories?

Again - if anyone can explain what maven is doing in order to look-up the
plugin location, that would be helpful.

Thanks,

Alex

alexworden wrote:

Wayne Fay wrote:

The plugin 'org.apache.maven.plugins:maven-eclipse-plugin' does not
exist or
no valid version could be found

From what I gather, maven should look in:
http://repo1.maven.org/maven2/eclipse/ but when I browse there, I
don't
find
any versions available. Is there something wrong with the maven
repository
right now? very mysterious...

This is incorrect. The correct url is:

http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-eclipse-plugin/

Wayne

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

--
View this message in context:
http://www.nabble.com/How-does-maven-resolve-plugin-dependencies-tf4694740s177.html#a13432043
Sent from the Maven - Users mailing list archive at Nabble.com.

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

--
View this message in context:
http://www.nabble.com/How-does-maven-resolve-plugin-dependencies-tf4694740s177.html#a13433842
Sent from the Maven - Users mailing list archive at Nabble.com.

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

Re: How can I get the path for a root pom.xml's basedir in a multimodule project with pom inheritance

2007-10-26 Thread Matthew McCullough

This is a creative idea, but appears only to work if your leaf nodes of the
project are all at the same level so that the ../../ is consistently just
the right amount back up the directory tree.

For example, it doesn't appear to work on a project structure like this,
where each node has a pom.xml:

-MatthewsProject
+Core
+Server
+Client
+Optional

It works for Server and Client, but Core and Optional complain because they
are reaching one level too far out for the parent.

Suggestions? Is this consistent with what you are seeing as well if you
have a 2 and 3 level deep tree of projects?

Sincerely,
Matthew McCullough
Managing Partner
Ambient Ideas, LLC

clamb wrote:

OK, i've been fighting this battle for a few days now and have a fairly
ugly solution.

in every pom.xml define a common root property:

properties
rootPOM${basedir}/..//rootPOM
/properties

Ensure that you have enough ../ to reference the rootPOM directory.

Everywhere you need to refer to this super root directory use ${rootPOM}.

Matthew McCullough wrote:

My far-from-modern CM group requires that we check in the binary
artifacts for our 3ps, and depend on them from a VOB checked out of
ClearCase. So our repo, as is now supported in Maven 2, is a
file://../../3pvob type of path rather than an HTTP path.

Let me know if you have any more ideas on this. And thanks again all.

-Matthew

--
View this message in context:
http://www.nabble.com/How-can-I-get-the-path-for-a-root-pom.xml%27s-basedir-in-a-multimodule-project-with-pom-inheritance-tf4577123s177.html#a13434309
Sent from the Maven - Users mailing list archive at Nabble.com.

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

Re: How can I get the path for a root pom.xml's basedir in a multimodule project with pom inheritance

2007-10-26 Thread clamb



Matthew McCullough wrote:
 
 This is a creative idea, but appears only to work if your leaf nodes of
 the project are all at the same level so that the ../../ is consistently
 just the right amount back up the directory tree.
 

Yeah ... that is a limitation. However, once you have each pom.xml setup its
no longer a problem.

The following worked for me (maven 2.0.4) as each mvn invocation at a
particular level has the rootPOM defined according to its own path. I've got
a project that goes 4 directories deep and am using this in the root pom.xml
for setting pluginDefaults so i can have my filters for the entire project
in one directory. 

  build
pluginManagement
plugins
plugin
inheritedtrue/inherited
...
configuration
defs${rootPOM}/genericFilters/defs
/configuration
...
/plugin
/plugins
/pluginManagement
  /build


-MatthewsProject   rootPOM${basedir}/rootPOM
+Core rootPOM${basedir}/..//rootPOM
+Server  rootPOM${basedir}/../..//rootPOM
+ClientrootPOM${basedir}/../..//rootPOM
+OptionalrootPOM${basedir}/..//rootPOM


-- 
View this message in context: 
http://www.nabble.com/How-can-I-get-the-path-for-a-root-pom.xml%27s-basedir-in-a-multimodule-project-with-pom-inheritance-tf4577123s177.html#a13434676
Sent from the Maven - Users mailing list archive at Nabble.com.


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

Re: Newbie to Continuum - help needed with first build error

2007-10-26 Thread olivier lamy

Hi,
Don't use the ViewVC.
You have to use directly the svn url.

--
Olivier

2007/10/26, Mick Ken [EMAIL PROTECTED]:

 Hi Guys,
 First of all let me tell you that I am new to this whole world of
 Continous Integration Server.I thought of trying it out, and as
 Apache is the best, I preferred to go with Continuum over others.So,
 please forgive my ignorance.

 I have added a ant based project using the web interface but when I
 try to build the project is throws this build error:

 Provider message: No such provider: ''

 I did the following so far:
 1. Created a new Project Group
 2. Added a new Ant project
 3. Provided my ViewVC url 
 http://localhost/subversion/trunk/?root=projectName
 4. Tried to build it and failed

 I think I am missing something and tried to go through the documents,
 but could not get much information. I would like to know  the
 following:

 1. Do  I have to change my project's build.xml to make it work with
 continuum?
 2. What is this pom.xml ?? Do I have to create that file and add in to
 my project?

 I would appreciate if someone can help me here.

 Thanks
 Mick




-- 
Olivier

help / Maven presentations

2007-10-26 Thread Marco Mistroni

hi all,
  i have finally convinced my workplace to move to maven (wasn't that
difficult, the alternative was a 500 line ant script which was very
volatile)

as i have learned maven by just using it and trying new feature all the
time, i'll appreciate if anyone could mail me privately some maven
presentation
that he /she has already used..
if anyone could help, that will be appreciated... you could mail me
privately at [EMAIL PROTECTED]

thanks in advancea nd regards


marco

Newbie to Continuum - help needed with first build error

2007-10-26 Thread Mick Ken

Hi Guys,
First of all let me tell you that I am new to this whole world of
Continous Integration Server.I thought of trying it out, and as
Apache is the best, I preferred to go with Continuum over others.So,
please forgive my ignorance.

I have added a ant based project using the web interface but when I
try to build the project is throws this build error:

Provider message: No such provider: ''

I did the following so far:
1. Created a new Project Group
2. Added a new Ant project
3. Provided my ViewVC url http://localhost/subversion/trunk/?root=projectName
4. Tried to build it and failed

I think I am missing something and tried to go through the documents,
but could not get much information. I would like to know  the
following:

1. Do  I have to change my project's build.xml to make it work with continuum?
2. What is this pom.xml ?? Do I have to create that file and add in to
my project?

I would appreciate if someone can help me here.

Thanks
Mick

Re: How can I get the path for a root pom.xml's basedir in a multimodule project with pom inheritance

2007-10-26 Thread Jörg Schaible

clamb wrote:

 
 
 Matthew McCullough wrote:
 
 This is a creative idea, but appears only to work if your leaf nodes of
 the project are all at the same level so that the ../../ is consistently
 just the right amount back up the directory tree.
 
 
 Yeah ... that is a limitation. However, once you have each pom.xml setup
 its no longer a problem.
 
 The following worked for me (maven 2.0.4) as each mvn invocation at a
 particular level has the rootPOM defined according to its own path. I've
 got a project that goes 4 directories deep and am using this in the root
 pom.xml for setting pluginDefaults so i can have my filters for the entire
 project in one directory.
 
   build
 pluginManagement
 plugins
 plugin
 inheritedtrue/inherited
 ...
 configuration
 defs${rootPOM}/genericFilters/defs
 /configuration
 ...
 /plugin
 /plugins
 /pluginManagement
   /build

Why don't you simply keep those filters in an own module and pack them into
an archive? Every other project that needs to access them may declare a dep
on that artifact and can user the build-helper plugin to unpack them into a
temporary location.

- Jörg


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

Re: How can I get the path for a root pom.xml's basedir in a multimodule project with pom inheritance

2007-10-26 Thread clamb



Jörg Schaible-2 wrote:
 
 Why don't you simply keep those filters in an own module and pack them
 into
 an archive? Every other project that needs to access them may declare a
 dep
 on that artifact and can user the build-helper plugin to unpack them into
 a
 temporary location.
 
 - Jörg
 

Two reasons:

 1) I'm really new at maven and i still haven't gotten 100% into the maven
packaging mindset. When i have more time i'll investigate your suggestion
closer.

 2) It seems non-intuitive to bundle 4 xml files into an archive, then
expand that archive out before i compile my java files ('cause i need to
filter them) for all 12 of my sub-projects vs: have my sub-project simply
point to the filter in the parent.

-- 
View this message in context: 
http://www.nabble.com/How-can-I-get-the-path-for-a-root-pom.xml%27s-basedir-in-a-multimodule-project-with-pom-inheritance-tf4577123s177.html#a13435319
Sent from the Maven - Users mailing list archive at Nabble.com.


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

Re: Issues with recent update of maven-changes-plugin

2007-10-26 Thread Dennis Lundberg

I have added 2.0-beta-2 to the metadata and updated the checksums in the 
Apache repo. This will be synced to the central repo in a couple of hours.


LAMY Olivier wrote:

Looks to be only a workaround.
It's not normal to not have 2.0-beta-2 in the metadata here :
http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-changes-plugin/maven-metadata.xml

--
Olivier  


-Message d'origine-
De : Geraud Geraud [mailto:[EMAIL PROTECTED] 
Envoyé : vendredi 26 octobre 2007 15:39

À : Maven Users List
Objet : Re: Issues with recent update of maven-changes-plugin

Thanks! I've forced the version to 2.0-beta2 and it worked.

--
Géraud

On 10/26/07, LAMY Olivier [EMAIL PROTECTED] wrote:

Have you try with force the  maven-changes-plugin version to 2.0-beta-2 or using a 
mvn version = 2.0.6 ?

--
Olivier

-Message d'origine-
De : Geraud Geraud [mailto:[EMAIL PROTECTED] Envoyé : vendredi 26 
octobre 2007 12:32 À : Maven Users List Objet : Issues with recent 
update of maven-changes-plugin


Hi,

it seems that the maven-metadata.xml at repo1.maven.org is incomplete
: it doesn't refer to the version 2.0-beta-2, so I cannot build maven site on 
my project (because I'm using Maven 2.0.5).

The error is:
[INFO] Ignoring available plugin update: 2.0-beta-3 as it requires 
Maven version 2.0.6 [INFO] 
--

--
[ERROR] BUILD ERROR
[INFO] 
--
-- [INFO] The plugin 'org.apache.maven.plugins:maven-changes-plugin' 
does not exist or no valid version could be found



Can anyone help?
Thanks.
--
Géraud

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


This e-mail, any attachments and the information contained therein (this 
message) are confidential and intended solely for the use of the addressee(s). If 
you have received this message in error please send it back to the sender and delete it. 
Unauthorized publication, use, dissemination or disclosure of this message, either in 
whole or in part is strictly prohibited.
--

Ce message électronique et tous les fichiers joints ainsi que  les informations contenues 
dans ce message ( ci après le message ), sont confidentiels et destinés 
exclusivement à l'usage de la  personne à laquelle ils sont adressés. Si vous avez reçu 
ce message par erreur, merci  de le renvoyer à son émetteur et de le détruire. Toutes 
diffusion, publication, totale ou partielle ou divulgation sous quelque forme que se soit 
non expressément autorisées de ce message, sont interdites.
--
---


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




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

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





--
Dennis Lundberg


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

Re: Maven checkstyle plugin, multimodule conf problem

2007-10-26 Thread Jim Sellers

Have not used this myself, but...
http://mojo.codehaus.org/dashboard-maven-plugin/

HTH
Jim


On 10/26/07, vetalok [EMAIL PROTECTED] wrote:


 Hello experts!
 I have the following structure:
 whizbang
 |-- pom.xml
 |-- a
 |   `-- pom.xml
 |   `-- target/site/checkstyle.html
 |-- b
 |   `-- pom.xml
 |   `-- target/site/checkstyle.html
 These checkstyle.htmls were created by running mvn checkstyle:checkstyle
 comand in whizbang directory.
 How can I autamatically combine all these  checkstyle.htmls into single
 checkstyle.html?
 Thanks.

 --
 View this message in context:
 http://www.nabble.com/Maven-checkstyle-plugin%2C-multimodule-conf-problem-tf4697789s177.html#a13428818
 Sent from the Maven - Users mailing list archive at Nabble.com.


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

Re: Newbie to Continuum - help needed with first build error

2007-10-26 Thread Mick Ken

Hi Oliver,
Thanks for that great help. I changed the ViewVC url to a Maven SCM
url and my first build using Continuum was generated successfully.

But I have one question here.To make the build,I had to also change
the Global settings of Continuum to point to my checked out working
folder i.e:

Working Folder:
C:\Working Folder\Project1

Build Folder:
C:\Working Folder\Project1\trunk\build

Deployment Folder:
C:\Working Folder\Project1\dist

And it works for one project,but how would I be able to generate
builds for other Projects i.e Project 2  ???

And other thing is, I have specified a deployment folder where I would
like the build output to go,but after the build i see Continuum
created a new folder named 5 and places the output there ??

Your pointers would be really appreciated.
Thanks



On 10/26/07, olivier lamy [EMAIL PROTECTED] wrote:
 Hi,
 Don't use the ViewVC.
 You have to use directly the svn url.

 --
 Olivier

 2007/10/26, Mick Ken [EMAIL PROTECTED]:
 
  Hi Guys,
  First of all let me tell you that I am new to this whole world of
  Continous Integration Server.I thought of trying it out, and as
  Apache is the best, I preferred to go with Continuum over others.So,
  please forgive my ignorance.
 
  I have added a ant based project using the web interface but when I
  try to build the project is throws this build error:
 
  Provider message: No such provider: ''
 
  I did the following so far:
  1. Created a new Project Group
  2. Added a new Ant project
  3. Provided my ViewVC url 
  http://localhost/subversion/trunk/?root=projectName
  4. Tried to build it and failed
 
  I think I am missing something and tried to go through the documents,
  but could not get much information. I would like to know  the
  following:
 
  1. Do  I have to change my project's build.xml to make it work with
  continuum?
  2. What is this pom.xml ?? Do I have to create that file and add in to
  my project?
 
  I would appreciate if someone can help me here.
 
  Thanks
  Mick
 



 --
 Olivier

How to get the list of modules in multi-modules build?

2007-10-26 Thread Yan Huang

Hello,

I'm wondering if there is a way to get the list of modules in the top level
of pom.xml? For example, I have 3 modules defined in a top level's pom.xml.
Now, if I want to run a antrun plugin in that pom.xml to get the list of
modules that are just built, how can i do it?

Thanks
Yan

Re: Debugging failes junit test

2007-10-26 Thread Jim Sellers

Take a look at
target/surefire-reports

In eclipse everything in src/main can see (on the classpath) src/test and
vis versa.

When running the tests, code in src/main cannot see src/test.

That might be it, but check out the output in the target/surefire-reports
for your specific issue.

HTH
Jim


On 10/25/07, Jan Torben Heuer [EMAIL PROTECTED] wrote:

 Hi,

 I have a problem with a junit test that failes when I run mvn test - but
 it does not fail when I run the test by the eclipse-junit-plugin.

 My problem ist, that there are no information:

 [...]
 Running ogcoperations.SubscriptionTest
 Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.009 sec
  FAILURE!
 Running core.LauncherTest
 Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.017 sec
  FAILURE!

 Results :

 Tests in error:

 testHandleXMLSubscribeDocumentImpl(
 core.handler.ogcoperations.SubscriptionTest)
   testGetSubscriber(core.handler.ogcoperations.SubscriptionTest)
   testStartup(core.LauncherTest)
 [...]

 even running maven with mvn -e -X test does not create more output.
 I have no idea why this test fails.

 How can I get the reason for the fail (assertion error, for example)
 Are there known problems with the plugin? Or other cases where the test
 only
 fail in maven but not in the IDE?


 Jan



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

Re: Newbie to Continuum - help needed with first build error

2007-10-26 Thread olivier lamy

Don't change the continuum settings as this.
use real working directory
/tmp/WorkingDirectory

/tmp/BuildOutputDirectory
On this two directories you will have projects in folders with their id.

Concerning deployment it's not supported with ant because continuum don't
know what deploy (an ant script can produce some artifacts).
This works with maven2 because continuum can extract some informations from
the pom to know what he have to deploy.


--
Olivier

2007/10/26, Mick Ken [EMAIL PROTECTED]:

 Hi Oliver,
 Thanks for that great help. I changed the ViewVC url to a Maven SCM
 url and my first build using Continuum was generated successfully.

 But I have one question here.To make the build,I had to also change
 the Global settings of Continuum to point to my checked out working
 folder i.e:

 Working Folder:
 C:\Working Folder\Project1

 Build Folder:
 C:\Working Folder\Project1\trunk\build

 Deployment Folder:
 C:\Working Folder\Project1\dist

 And it works for one project,but how would I be able to generate
 builds for other Projects i.e Project 2  ???

 And other thing is, I have specified a deployment folder where I would
 like the build output to go,but after the build i see Continuum
 created a new folder named 5 and places the output there ??

 Your pointers would be really appreciated.
 Thanks



 On 10/26/07, olivier lamy  [EMAIL PROTECTED] wrote:
  Hi,
  Don't use the ViewVC.
  You have to use directly the svn url.
 
  --
  Olivier
 
  2007/10/26, Mick Ken  [EMAIL PROTECTED]:
  
   Hi Guys,
   First of all let me tell you that I am new to this whole world of
   Continous Integration Server.I thought of trying it out, and as
   Apache is the best, I preferred to go with Continuum over others.So,
   please forgive my ignorance.
  
   I have added a ant based project using the web interface but when I
   try to build the project is throws this build error:
  
   Provider message: No such provider: ''
  
   I did the following so far:
   1. Created a new Project Group
   2. Added a new Ant project
   3. Provided my ViewVC url 
   http://localhost/subversion/trunk/?root=projectName
   4. Tried to build it and failed
  
   I think I am missing something and tried to go through the documents,
   but could not get much information. I would like to know  the
   following:
  
   1. Do  I have to change my project's build.xml to make it work with
   continuum?
   2. What is this pom.xml ?? Do I have to create that file and add in to
   my project?
  
   I would appreciate if someone can help me here.
  
   Thanks
   Mick
  
 
 
 
  --
  Olivier
 




-- 
Olivier

Re: dependencies outside maven

Wayne, Graham, thanks for your advices !

I will investigate a bit the scopesystem/scope bug/feature (havent
really heard of it yet).

Is it possible to have maven run a script before dependency checking ?
That would allow us to have a script (or maven-plugin, or ant task,
or whatever) run as part of the build that would download our
dependencies and install them locally. That would be mostly
transparent to the developer, so it looks like a clean solution.

Worst case, we can always have a separate script that the developer
has to run prior to run maven, but it is not as clean ...

I know, I should try it before asking the question ... but ... I'm a
bit lazy, and it's already the weekend ...

Thanks again !

MrG

Our migration isnt only a large complex project, its dozen of them !
Each project generating many artifacts ... So yes, in the best world,
if everything goes right, I think we can expect to complete the
migration in a few years ;-) Every step to ease that pain will be
welcomed.

I will certainly have to write some documentation of our process, but
in french (sorry). I will let you know if I am allowed to publish it
...

On 26/10/2007, Wayne Fay [EMAIL PROTECTED] wrote:
 You can try to use scopesystem/scope bug this is generally not
 encouraged as it does not work as you might expect in all situations.
 This would allow you to pull your artifacts from your current system,
 put them in a /lib folder, and use them as part of your current Maven
 build.

 However, I think this is a bad idea -- system scope is not a long-term
 solution, and not a great short-term solution either. Instead I would
 build a little shell script that would analyze your pom, go out to
 your proprietary repo and download the necessary files and then use
 mvn install:install-file -DgeneratePom=true -DcreateChecksum=true
 ... to install each one into your local Maven repo cache.

 Ideally once you got things working on your local environment, you
 would use mvn deploy to deploy your code to a new Maven (corporate)
 repo that you will set up that will function as your new artifact
 repository. I would also write a script to run mvn
 deploy:deploy-file similar to the mvn install script mentioned
 above, so you will migrate not only the current app you're working on
 but also all of its related support libraries etc.

 Wayne

 On 10/26/07, Guillaume Lederrey [EMAIL PROTECTED] wrote:
  On 26/10/2007, Graham Leggett [EMAIL PROTECTED] wrote:
   On Fri, October 26, 2007 4:01 pm, Guillaume Lederrey wrote:
  
The dependencies on standard jars is not really a problem for us. As
you say, most of them are available already, and they tend not to
change to often.
   
Our problem comes from dependencies on internally produced jars. For
example, we have a team working on a Swing Framework used by most of
our projects, or many teams working on components / services reused by
other internal projects. Those artifacts are deployed fairly often in
our proprietary repository, and we have to be able to depend on them.
   
It is not an option to build a dependency graph and migrate first the
projects on which other projects depends. And it would be pretty heavy
to manually update our maven repository to include new versions of our
framework every time they do a release.
   
For example, we need to be able to keep the framework deployed to our
proprietary repo, but have dependencies to this framework from
projects already migrating to maven.
  
   You need to start at the bottom of your dependency tree, with those
   dependencies that do not depend on other internal dependencies.
 
   That's our main problem !
 
   For organizational / political reasons, the bottom of our
  dependency tree will not migrate anytime soon ... that's why we need
  some way to depend on projects NOT in the maven repository ...
 
   I know, we're going to have a lot of fun !
 
   Get these bottom-most dependencies to the point where they are built by
   and deployed by maven to an internal maven repository set up for your
   project.
  
   When you make a release of these bottom dependencies, go through the
   formal maven release procedure (use the release plugin for this to make it
   easy), and as a final step, copy the artifact from the maven repository
   into your prorietry repo.
  
   Eventually, over time, more of the code will start life in the maven repo,
   until eventually you phase the proprietry repo out entirely. You can do
   this as quickly or as slowly as you feel comfortable with.
  
   Regards,
   Graham
   --
  
  
  
   -
   To unsubscribe, e-mail: [EMAIL PROTECTED]
   For additional commands, e-mail: [EMAIL PROTECTED]
  
  
 
 
  --
  Jabber : [EMAIL PROTECTED]
  Skype : Guillaume.Lederrey
  Projects :
  * http://rwanda.wordpress.com/
  * http://rwandatech.wordpress.com/

Re: dependencies outside maven