Re: how to exclude modules
1- I know, but sadly it is not enough to justify the move to my manager! :( 2- Good idea, I can define a profile per module + 1 for all, and enable only the specific profiles I need. My only problem is that the release plugin will still update all dependencies to SNAPSHOT in my webapp pom, I'm not sure I like that idea, maybe I can patch the plugin to work differently! Thanks for your help! On 23/04/07, Wayne Fay [EMAIL PROTECTED] wrote: 1. Move to Subversion. File refactoring does not lose history. 2. There is no module excludes. Instead we have a notion of profiles in M2. So you would set your default in the top parent pom.xml to have say either zero or very few modules defined, and then in a separate profile (call it all), you would have all modules listed. Thus when you normally built your project from the top parent dir, only the default modules would be built. But then when you specified -Pall, all your modules would be built. Perhaps this gives you something to think about. I'm not sure if it solves all your problems. Wayne On 4/23/07, Daniel Beland [EMAIL PROTECTED] wrote: Hi, I have some questions about aggregation modules in maven2. Let me explain how we were working with maven 1.1 and why I don`t fully understand how we should work with maven 2. We have some maven 1 multi-projects saved in CVS as a single project. A developer checks out the complete project in 1 operation. Most of the time, it consists of N jar artifacts to be included in a webapp. Since we do not modify all the N artifacts but just a subset of them between each release, we would work intensively with the maven.multiproject.excludesproperty to set only the projects we want to build between each release (projects that are SNAPSHOT and are needed in the webapp project.xml, and it means we reset the value to all projects every time we release a beta). Since the rest is already released (be it production version or previous unchanged beta), there is no need to compile and deploy them again the next time. Now in maven 2, there is no such property. After a release, everything is put back to SNAPSHOT, even all the dependencies in the webapp pom (as I understand it would do). How can I release a project and have only each artifact's current version set to SNAPSHOT, but have the webapp dependencies left to the just released version? (Keep in mind I didn't release an aggregation module with inter-dependencies yet and maybe it is not what it does). How can I have something similar to maven.multiproject.excludes? Should I comment the modules I don't want to compile in the pom? Finally, is it in your opinion better to simply have N projects in CVS other than a big aggregation project to achieve what I want? (But would still use the same parent pom, I would just release each sub-module independently and have better control on what to release each time). My only concern with that is the major refactoring of the CVS modules and losing all the file history. Thanks for your input, Daniel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Include optional dependencies
Hi, I am presently converting our projects from maven 1.1 to maven 2. I must say that the transitive dependencies help a lot to reduce the pom and makes upgrades easier. But I would like to include optional dependencies as well, without having to explicitly include them myself in the pom. For example, I use hibernate 3.2.1.ga, it has an optional dependency on jgroups-all-2.2.8. I would like to be able to add an includes statement on the hibernate lib to tell that I want to include jgroups as well. The main reason for this, is that I want the same version as specified in the hibernate pom. This way, upgrading hibernate would also upgrade my version of jgroups at the same time. The only problem I can see though, is how can we set if this dependency should be optional or not when this artifact is used in another project. We would have to be able to set optional on the included transitive dependency. So I thought it could probably be better if we could set the dependency explicitly in the pom without specifying the version and have maven resolve the version from the nearest source (as it does normally) and fail if no other source of the lib can be found in the resolution tree. But this would mean more flexibility on the pom and could be hard to implement. Otherwise, I know we can use a dependencyManagement on a parent pom. But if I set this in the parent pom: dependency groupIdjgroups/groupId artifactIdjgroups-all/artifactId version2.2.8/version /dependency and don't set the version in my project, how will maven react when hibernate upgrades the dependency? Will it use the parent pom version or the hibernate version as the nearest source? What are your thoughts on the subject? Is this something other people would find useful as well? Am I bothering about something that does not happen often with maven 2 and should take it as it is? Thanks for your input, Daniel
how to exclude modules
Hi, I have some questions about aggregation modules in maven2. Let me explain how we were working with maven 1.1 and why I don`t fully understand how we should work with maven 2. We have some maven 1 multi-projects saved in CVS as a single project. A developer checks out the complete project in 1 operation. Most of the time, it consists of N jar artifacts to be included in a webapp. Since we do not modify all the N artifacts but just a subset of them between each release, we would work intensively with the maven.multiproject.excludesproperty to set only the projects we want to build between each release (projects that are SNAPSHOT and are needed in the webapp project.xml, and it means we reset the value to all projects every time we release a beta). Since the rest is already released (be it production version or previous unchanged beta), there is no need to compile and deploy them again the next time. Now in maven 2, there is no such property. After a release, everything is put back to SNAPSHOT, even all the dependencies in the webapp pom (as I understand it would do). How can I release a project and have only each artifact's current version set to SNAPSHOT, but have the webapp dependencies left to the just released version? (Keep in mind I didn't release an aggregation module with inter-dependencies yet and maybe it is not what it does). How can I have something similar to maven.multiproject.excludes? Should I comment the modules I don't want to compile in the pom? Finally, is it in your opinion better to simply have N projects in CVS other than a big aggregation project to achieve what I want? (But would still use the same parent pom, I would just release each sub-module independently and have better control on what to release each time). My only concern with that is the major refactoring of the CVS modules and losing all the file history. Thanks for your input, Daniel
How to change the invoked goals at runtime
Hi,
I am trying to migrate our projects to maven 2.0.5 (have been using maven 1
for 2 years now).
I would like to know how I can invoke maven to package the artifact only
when the version does not contain SNAPSHOT, and install it if it contains
SNAPSHOT.
In maven 1 I was using a goal like this:
goal name=jar:cruisecontrol
j:if test=${not(pom.currentVersion.endsWith('SNAPSHOT'))}
ant:echo message=Create jar only/
attainGoal name=jar/
/j:if
j:if test=${pom.currentVersion.endsWith('SNAPSHOT')}
ant:echo message=Install SNAPSHOT jar/
attainGoal name=jar:install/
/j:if
/goal
This is because I do not want cruise control to install an artifact if it is
not a SNAPSHOT. (Released version should always be downloaded from our
central repository).
It happened too many times that developers forget to change the version to
SNAPSHOT after a release, and we overwrite the local artifact and break the
build of other modules.
Profiles cannot be called based on ${pom.version} ending with SNAPSHOT.
I checked the plugin development, but I didn't find how we can alter the
goals from a plugin.
Someone has an idea how I can attain this?
Thanks,
Daniel
Re: How to change the invoked goals at runtime
Ok let me explin it with more details.
I have projects A, B and C, giving artifacts a-1.0.jar, b-1.0.war and
c-1.0.war.
B as a dependency on a-1.0.jar
C as a dependency on a-1.0.jar.
We modify A and B only = (A version should become a-1.1-SNAPSHOT.jar)
But the developer commit it and forget to change the version, the local lib
a-1.0.jar is installed over with what should have been a-1.1-SNAPSHOT.jar.
The build of B breaks because a-1.1-SNAPSHOT.jar cannot be found, he
realizes it and change it. Everything seems ok from now on, no harms done.
We make a modification to C later, build of C breaks, we don't understand
why and can spend a long time trying to find out the reason (because the
local lib a-1.0.jar is not the same as on the central repository). We have
to delete it from the local repository to make sure it is downloaded
properly next time.
To make sure this kind of situation does not happen again, I would like to
install the artifacts only when the version is SNAPSHOT. With cruise control
I cannot configure it to build the project only when the version is
SNAPSHOT. I need to find a way to do it within the maven build lifecycle.
On 08/03/07, Jerome Lacoste [EMAIL PROTECTED] wrote:
On 3/8/07, Daniel Beland [EMAIL PROTECTED] wrote:
Hi,
I am trying to migrate our projects to maven 2.0.5 (have been using
maven 1
for 2 years now).
I would like to know how I can invoke maven to package the artifact only
when the version does not contain SNAPSHOT, and install it if it
contains
SNAPSHOT.
In maven 1 I was using a goal like this:
goal name=jar:cruisecontrol
j:if test=${not(pom.currentVersion.endsWith('SNAPSHOT'))}
ant:echo message=Create jar only/
attainGoal name=jar/
/j:if
j:if test=${pom.currentVersion.endsWith('SNAPSHOT')}
ant:echo message=Install SNAPSHOT jar/
attainGoal name=jar:install/
/j:if
/goal
This is because I do not want cruise control to install an artifact if
it is
not a SNAPSHOT. (Released version should always be downloaded from our
central repository).
install will only happen under the local repository of the user
running your cruisecontrol instance. Why is that affecting you ?
It happened too many times that developers forget to change the version
to
SNAPSHOT after a release, and we overwrite the local artifact and break
the
build of other modules.
If that's the root of your problem, use the release plugin and it
should disappear.
J
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to change the invoked goals at runtime
I had a look at the new release plugin, saw what you mean, It will update
the version back to SNAPSHOT, nice little feature that was missing in maven
1.
Thanks for your help
On 08/03/07, Daniel Beland [EMAIL PROTECTED] wrote:
Hi,
I am trying to migrate our projects to maven 2.0.5 (have been using maven
1 for 2 years now).
I would like to know how I can invoke maven to package the artifact only
when the version does not contain SNAPSHOT, and install it if it contains
SNAPSHOT.
In maven 1 I was using a goal like this:
goal name=jar:cruisecontrol
j:if test=${not(pom.currentVersion.endsWith('SNAPSHOT'))}
ant:echo message=Create jar only/
attainGoal name=jar/
/j:if
j:if test=${pom.currentVersion.endsWith('SNAPSHOT')}
ant:echo message=Install SNAPSHOT jar/
attainGoal name=jar:install/
/j:if
/goal
This is because I do not want cruise control to install an artifact if it
is not a SNAPSHOT. (Released version should always be downloaded from our
central repository).
It happened too many times that developers forget to change the version to
SNAPSHOT after a release, and we overwrite the local artifact and break the
build of other modules.
Profiles cannot be called based on ${ pom.version} ending with SNAPSHOT.
I checked the plugin development, but I didn't find how we can alter the
goals from a plugin.
Someone has an idea how I can attain this?
Thanks,
Daniel
Re: [m1.1] artifactId or id?
I am using the build of 2006-07-23. Whenever I do jar:install or jar:deploy or war:install or war:deploy it does it. Same thing for struts-module plugin or other custom plugins I developed. It seems to come directly from the maven code as it is common to all plugins I've tried. If I have the following code in the POM: idid/id groupIdgroup/groupId artifactIdartifact/artifactId currentVersion2.11-beta2/currentVersion Here is the trace: __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.1-beta-3-SNAPSHOT build:start: java:prepare-filesystem: java:compile: xdoclet:hibernatedoclet: fix-foreign-keys: [echo] Compiling to c:\eclipse\workspace\DBInterface/target/classes [echo] == WARNING: maven.compile.target is not set: using the default value which depends on your JVM == java:jar-resources: copy-hbm-files: test:test: jar:jar: jar:install: [echo] Installing... Uploading to group/jars/id-2.11-beta2.jar: (467K) Uploading to group/poms/id-2.11-beta2.pom: (16K) BUILD SUCCESSFUL Total time : 12 seconds Finished at : Monday, July 31, 2006 10:02:49 BST AM I'll open a bug in jira On 7/29/06, Lukas Theussl [EMAIL PROTECTED] wrote: Where did you read that in maven 1.1 id is used instead of artifactId? It should be just the other way round, we have replaced id by the combination groupIdartifactId. However, there are probably still some inconsistencies (see eg [1]), so it would be good to know where you ran into problems with this? Cheers, -Lukas [1] http://jira.codehaus.org/browse/MAVEN-1704 Daniel Beland wrote: Hi, in maven 1.0.2, when I install or deploy an artifact, it is put in the groupId directory under types and the artifact is named artifactId.type Now in maven 1.1, the artifact is named id instead of artifactId. I was not using this tag previously I think Mevenide defaults it to groupId:artifactId so obviously it causes problems because it is not named as before and it is not deployed at all (I think the colon is not supported in the file name). On the web site it says this: id The short name of the project. This value is used when naming jarshttp://maven.apache.org/maven-1.x/plugins/java/index.htmland distribution files http://maven.apache.org/maven-1.x/plugins/dist/index.html. groupId The short name of the project group. This value is used to group all jars for a project in one directory. For more info look at the user guidehttp://maven.apache.org/maven-1.x/reference/conventions.html. artifactId The short name of the project. This value is used in conjunction with groupId when naming jarshttp://maven.apache.org/maven-1.x/plugins/java/index.htmland distribution files http://maven.apache.org/maven-1.x/plugins/dist/index.html. I don't mind updating all my project files, I just want to make sure it is the expected behaviour from now on before I do it? Thanks, Daniel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m1.1] artifactId or id?
Hi, in maven 1.0.2, when I install or deploy an artifact, it is put in the groupId directory under types and the artifact is named artifactId.type Now in maven 1.1, the artifact is named id instead of artifactId. I was not using this tag previously I think Mevenide defaults it to groupId:artifactId so obviously it causes problems because it is not named as before and it is not deployed at all (I think the colon is not supported in the file name). On the web site it says this: id The short name of the project. This value is used when naming jarshttp://maven.apache.org/maven-1.x/plugins/java/index.htmland distribution files http://maven.apache.org/maven-1.x/plugins/dist/index.html. groupId The short name of the project group. This value is used to group all jars for a project in one directory. For more info look at the user guidehttp://maven.apache.org/maven-1.x/reference/conventions.html. artifactId The short name of the project. This value is used in conjunction with groupId when naming jarshttp://maven.apache.org/maven-1.x/plugins/java/index.htmland distribution files http://maven.apache.org/maven-1.x/plugins/dist/index.html. I don't mind updating all my project files, I just want to make sure it is the expected behaviour from now on before I do it? Thanks, Daniel
Re: [m1.1] Unable to deploy to remote repository
This is what I have: gdps,10.1.119.102 ssh-rsa B3NzaC1yc2EBIwAAAIEAz44256CBVYdZPIrtoRvbl4qUuj758/U81bcMHpDK1J/6kax4lUKX4edBW38e/BvAULs0WFeP7eyMaZVQVj5NFGgRYiqkNSsfEDwc3byq/6T8dA+cSs7BzEj380SyP6It93tW40JdSEN+7TP4/kYVND/tg0UFpSPnJnXNxm9kNTk= On 7/26/06, Lukas Theussl [EMAIL PROTECTED] wrote: How does the line with gdps in known_hosts look like exactly? Jsch expects a fully qualified hostname, ie something like gdps.domain.org,xxx.xxx.xxx.xxx ssh-rsa ... and not gdps ssh-rsa ... even though the latter works from the command line. HTH, -Lukas Daniel Beland wrote: Hi, yes I can logon with ssh, scp and sftp works perfectly fine. I already accepted to add the server to my list. I can se a line for gdps in the file ~/.ssh/known_hosts. I am not using authentication keys, I always type in the password. As I said, everything works fine with maven 1.0.2 and artifact plugin 1.5.2 Moving to maven 1.1-beta3 and artifact plugin 1.7 is causing me the problem. Since I am on windows and I run maven in cygwin, sometimes there are problems with the $HOME directories (my cygwin HOME is in /home of cygwin and in java it is the windows home in Documents And Settings). So I tried to copy my .ssh folder in my windows HOME and it is still the same. Is the new artifact plugin using the ssh ant task? If so I think the easiest solution would be to add the trust property to the plugin to skip this security check. thanks, Daniel On 7/25/06, Arnaud HERITIER [EMAIL PROTECTED] wrote: Hi Daniel, Did you try to logon to your proxy host using ssh ? ssh -l cvs gdps It will certainly ask if you want to accept permanently the key. Arnaud On 7/25/06, Daniel Beland [EMAIL PROTECTED] wrote: Hi, I have been using maven 1.0.2 for more than a year now. I use it to make all of our releases on our internal repository. I have setup maven-proxy to access that repository and eveything works fine. In my build.properties file I have the following settings: maven.repo.RF1=sftp://gdps maven.repo.RF1.username=cvs maven.repo.RF1.password=*** maven.repo.RF1.directory=/cvs/maven/repo-local I tried to migrate to maven 1.1-beta3-SNAPSHOT (20060723) and I am unable to deploy something to the remote repository. (I tried jar:deploy, plugin:repository-deploy, etc all with the same exception). My configuration seems ok based on the maven-artifact-plugin doc. Looking on google I saw that we need to put the trust attribute to true, (if it is the ant task that is used by maven), but didn't find any way to configure it. I absolutely have to use sftp or scp. Here is the complete exception trace: Failed to deploy to: RF1 Reason: org.apache.maven.wagon.authentication.AuthenticationException: Cannot connect. Reason: reject HostKey: gdps org.apache.maven.wagon.authentication.AuthenticationException: Cannot connect. Reason: reject HostKey: gdps at org.apache.maven.wagon.providers.ssh.AbstractSshWagon.openConnection( AbstractSshWagon.java:232) at org.apache.maven.wagon.AbstractWagon.connect( AbstractWagon.java :143) at org.apache.maven.wagon.AbstractWagon.connect( AbstractWagon.java :106) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deployFiles( DefaultArtifactDeployer.java:372) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.doDeploy( DefaultArtifactDeployer.java:320) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.handleDeploy ( DefaultArtifactDeployer.java:119) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy (DefaultArtifactDeployer.java:90) at org.apache.maven.artifact.deployer.DeployBean.deploy( DeployBean.java:155) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke( NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke( DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.commons.jelly.impl.DynamicBeanTag.doTag( DynamicBeanTag.java:180) at org.apache.commons.jelly.impl.StaticTagScript.run( StaticTagScript.java:102) at org.apache.commons.jelly.impl.ScriptBlock.run( ScriptBlock.java :95) at org.apache.commons.jelly.impl.DynamicTag.doTag( DynamicTag.java :79) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java :250) at org.apache.commons.jelly.impl.ScriptBlock.run( ScriptBlock.java :95) at org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag( MavenGoalTag.java:82) at org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction.performAction (MavenGoalTag.java:115) at org.apache.maven.werkz.Goal.fire(Goal.java:647
Re: [m1.1] Unable to deploy to remote repository
Settping though the code to debug what was going on, I saw that wagon handle putty (plink and pscp) differently than the rest. So I downloaded them and changed the protocol to scpexe. This works fine for me so I'll use that from now on. If scp and sftp works fine for everyone else, I guess we can put the problem on my windows+cygwin setup that does not work well with java. (It's not the first time I see that, for example it always read my .cvspass from my windows HOME directory even though I'm running it in cygwin. ie: java.user.home = windows home because java doesn't know about cygwin). So I think we can leave it as it is, though I would recommend a note on the web site to recommend putty for windows users that want to use ssh. Thanks for your help, Daniel On 7/27/06, Daniel Beland [EMAIL PROTECTED] wrote: This is what I have: gdps,10.1.119.102 ssh-rsa B3NzaC1yc2EBIwAAAIEAz44256CBVYdZPIrtoRvbl4qUuj758/U81bcMHpDK1J/6kax4lUKX4edBW38e/BvAULs0WFeP7eyMaZVQVj5NFGgRYiqkNSsfEDwc3byq/6T8dA+cSs7BzEj380SyP6It93tW40JdSEN+7TP4/kYVND/tg0UFpSPnJnXNxm9kNTk= On 7/26/06, Lukas Theussl [EMAIL PROTECTED] wrote: How does the line with gdps in known_hosts look like exactly? Jsch expects a fully qualified hostname, ie something like gdps.domain.org,xxx.xxx.xxx.xxx ssh-rsa ... and not gdps ssh-rsa ... even though the latter works from the command line. HTH, -Lukas Daniel Beland wrote: Hi, yes I can logon with ssh, scp and sftp works perfectly fine. I already accepted to add the server to my list. I can se a line for gdps in the file ~/.ssh/known_hosts. I am not using authentication keys, I always type in the password. As I said, everything works fine with maven 1.0.2 and artifact plugin 1.5.2 Moving to maven 1.1-beta3 and artifact plugin 1.7 is causing me the problem. Since I am on windows and I run maven in cygwin, sometimes there are problems with the $HOME directories (my cygwin HOME is in /home of cygwin and in java it is the windows home in Documents And Settings). So I tried to copy my .ssh folder in my windows HOME and it is still the same. Is the new artifact plugin using the ssh ant task? If so I think the easiest solution would be to add the trust property to the plugin to skip this security check. thanks, Daniel On 7/25/06, Arnaud HERITIER [EMAIL PROTECTED] wrote: Hi Daniel, Did you try to logon to your proxy host using ssh ? ssh -l cvs gdps It will certainly ask if you want to accept permanently the key. Arnaud On 7/25/06, Daniel Beland [EMAIL PROTECTED] wrote: Hi, I have been using maven 1.0.2 for more than a year now. I use it to make all of our releases on our internal repository. I have setup maven-proxy to access that repository and eveything works fine. In my build.properties file I have the following settings: maven.repo.RF1=sftp://gdps maven.repo.RF1.username=cvs maven.repo.RF1.password=*** maven.repo.RF1.directory=/cvs/maven/repo-local I tried to migrate to maven 1.1-beta3-SNAPSHOT (20060723) and I am unable to deploy something to the remote repository. (I tried jar:deploy, plugin:repository-deploy, etc all with the same exception). My configuration seems ok based on the maven-artifact-plugin doc. Looking on google I saw that we need to put the trust attribute to true, (if it is the ant task that is used by maven), but didn't find any way to configure it. I absolutely have to use sftp or scp. Here is the complete exception trace: Failed to deploy to: RF1 Reason: org.apache.maven.wagon.authentication.AuthenticationException : Cannot connect. Reason: reject HostKey: gdps org.apache.maven.wagon.authentication.AuthenticationException: Cannot connect. Reason: reject HostKey: gdps at org.apache.maven.wagon.providers.ssh.AbstractSshWagon.openConnection( AbstractSshWagon.java:232) at org.apache.maven.wagon.AbstractWagon.connect( AbstractWagon.java :143) at org.apache.maven.wagon.AbstractWagon.connect( AbstractWagon.java :106) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deployFiles ( DefaultArtifactDeployer.java:372) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.doDeploy ( DefaultArtifactDeployer.java:320) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.handleDeploy( DefaultArtifactDeployer.java:119) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy (DefaultArtifactDeployer.java:90) at org.apache.maven.artifact.deployer.DeployBean.deploy( DeployBean.java :155) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke( NativeMethodAccessorImpl.java:39
Re: [m1.1] Unable to deploy to remote repository
Hi, yes I can logon with ssh, scp and sftp works perfectly fine. I already accepted to add the server to my list. I can se a line for gdps in the file ~/.ssh/known_hosts. I am not using authentication keys, I always type in the password. As I said, everything works fine with maven 1.0.2 and artifact plugin 1.5.2 Moving to maven 1.1-beta3 and artifact plugin 1.7 is causing me the problem. Since I am on windows and I run maven in cygwin, sometimes there are problems with the $HOME directories (my cygwin HOME is in /home of cygwin and in java it is the windows home in Documents And Settings). So I tried to copy my .ssh folder in my windows HOME and it is still the same. Is the new artifact plugin using the ssh ant task? If so I think the easiest solution would be to add the trust property to the plugin to skip this security check. thanks, Daniel On 7/25/06, Arnaud HERITIER [EMAIL PROTECTED] wrote: Hi Daniel, Did you try to logon to your proxy host using ssh ? ssh -l cvs gdps It will certainly ask if you want to accept permanently the key. Arnaud On 7/25/06, Daniel Beland [EMAIL PROTECTED] wrote: Hi, I have been using maven 1.0.2 for more than a year now. I use it to make all of our releases on our internal repository. I have setup maven-proxy to access that repository and eveything works fine. In my build.properties file I have the following settings: maven.repo.RF1=sftp://gdps maven.repo.RF1.username=cvs maven.repo.RF1.password=*** maven.repo.RF1.directory=/cvs/maven/repo-local I tried to migrate to maven 1.1-beta3-SNAPSHOT (20060723) and I am unable to deploy something to the remote repository. (I tried jar:deploy, plugin:repository-deploy, etc all with the same exception). My configuration seems ok based on the maven-artifact-plugin doc. Looking on google I saw that we need to put the trust attribute to true, (if it is the ant task that is used by maven), but didn't find any way to configure it. I absolutely have to use sftp or scp. Here is the complete exception trace: Failed to deploy to: RF1 Reason: org.apache.maven.wagon.authentication.AuthenticationException: Cannot connect. Reason: reject HostKey: gdps org.apache.maven.wagon.authentication.AuthenticationException: Cannot connect. Reason: reject HostKey: gdps at org.apache.maven.wagon.providers.ssh.AbstractSshWagon.openConnection( AbstractSshWagon.java:232) at org.apache.maven.wagon.AbstractWagon.connect( AbstractWagon.java :143) at org.apache.maven.wagon.AbstractWagon.connect( AbstractWagon.java :106) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deployFiles( DefaultArtifactDeployer.java:372) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.doDeploy( DefaultArtifactDeployer.java:320) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.handleDeploy( DefaultArtifactDeployer.java:119) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy (DefaultArtifactDeployer.java:90) at org.apache.maven.artifact.deployer.DeployBean.deploy( DeployBean.java:155) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke( NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke( DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.commons.jelly.impl.DynamicBeanTag.doTag( DynamicBeanTag.java:180) at org.apache.commons.jelly.impl.StaticTagScript.run( StaticTagScript.java:102) at org.apache.commons.jelly.impl.ScriptBlock.run( ScriptBlock.java :95) at org.apache.commons.jelly.impl.DynamicTag.doTag( DynamicTag.java :79) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java :250) at org.apache.commons.jelly.impl.ScriptBlock.run( ScriptBlock.java :95) at org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag( MavenGoalTag.java:82) at org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction.performAction (MavenGoalTag.java:115) at org.apache.maven.werkz.Goal.fire(Goal.java:647) at org.apache.maven.werkz.Goal.attain(Goal.java:582) at org.apache.maven.plugin.PluginManager.attainGoals( PluginManager.java:709) at org.apache.maven.MavenSession.attainGoals(MavenSession.java :264) at org.apache.maven.cli.App.doMain(App.java:546) at org.apache.maven.cli.App.main(App.java:1359) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke( NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke( DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.werken.forehead.Forehead.run(Forehead.java:551
Re: [m1.1] Unable to deploy to remote repository
Sorry I was using 1.8 and not 1.7 as I said. 1.9-SNAPSHOT gives me the same error. On 7/26/06, Arnaud HERITIER [EMAIL PROTECTED] wrote: The new artifact plugin uses the wagon project. I must have a look at the code to see how it works. Can you try the version 1.9-SNAPSHOT please? maven plugin:download -DgroupId=maven -DartifactId=*maven-artifact-plugin* -Dversion=*1.9*-SNAPSHOT -Dmaven.repo.remote=http://www.ibiblio.org/maven, http://people.apache.org/repo/m1-snapshot-repository/ Cheers, Arnaud On 7/26/06, Daniel Beland [EMAIL PROTECTED] wrote: Hi, yes I can logon with ssh, scp and sftp works perfectly fine. I already accepted to add the server to my list. I can se a line for gdps in the file ~/.ssh/known_hosts. I am not using authentication keys, I always type in the password. As I said, everything works fine with maven 1.0.2 and artifact plugin 1.5.2 Moving to maven 1.1-beta3 and artifact plugin 1.7 is causing me the problem. Since I am on windows and I run maven in cygwin, sometimes there are problems with the $HOME directories (my cygwin HOME is in /home of cygwin and in java it is the windows home in Documents And Settings). So I tried to copy my .ssh folder in my windows HOME and it is still the same. Is the new artifact plugin using the ssh ant task? If so I think the easiest solution would be to add the trust property to the plugin to skip this security check. thanks, Daniel On 7/25/06, Arnaud HERITIER [EMAIL PROTECTED] wrote: Hi Daniel, Did you try to logon to your proxy host using ssh ? ssh -l cvs gdps It will certainly ask if you want to accept permanently the key. Arnaud On 7/25/06, Daniel Beland [EMAIL PROTECTED] wrote: Hi, I have been using maven 1.0.2 for more than a year now. I use it to make all of our releases on our internal repository. I have setup maven-proxy to access that repository and eveything works fine. In my build.properties file I have the following settings: maven.repo.RF1=sftp://gdps maven.repo.RF1.username=cvs maven.repo.RF1.password=*** maven.repo.RF1.directory=/cvs/maven/repo-local I tried to migrate to maven 1.1-beta3-SNAPSHOT (20060723) and I am unable to deploy something to the remote repository. (I tried jar:deploy, plugin:repository-deploy, etc all with the same exception). My configuration seems ok based on the maven-artifact-plugin doc. Looking on google I saw that we need to put the trust attribute to true, (if it is the ant task that is used by maven), but didn't find any way to configure it. I absolutely have to use sftp or scp. Here is the complete exception trace: Failed to deploy to: RF1 Reason: org.apache.maven.wagon.authentication.AuthenticationException: Cannot connect. Reason: reject HostKey: gdps org.apache.maven.wagon.authentication.AuthenticationException: Cannot connect. Reason: reject HostKey: gdps at org.apache.maven.wagon.providers.ssh.AbstractSshWagon.openConnection ( AbstractSshWagon.java:232) at org.apache.maven.wagon.AbstractWagon.connect( AbstractWagon.java :143) at org.apache.maven.wagon.AbstractWagon.connect( AbstractWagon.java :106) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deployFiles ( DefaultArtifactDeployer.java:372) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.doDeploy( DefaultArtifactDeployer.java:320) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.handleDeploy( DefaultArtifactDeployer.java:119) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy (DefaultArtifactDeployer.java:90) at org.apache.maven.artifact.deployer.DeployBean.deploy( DeployBean.java:155) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke( NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke( DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.commons.jelly.impl.DynamicBeanTag.doTag( DynamicBeanTag.java:180) at org.apache.commons.jelly.impl.StaticTagScript.run( StaticTagScript.java:102) at org.apache.commons.jelly.impl.ScriptBlock.run( ScriptBlock.java :95) at org.apache.commons.jelly.impl.DynamicTag.doTag( DynamicTag.java :79) at org.apache.commons.jelly.impl.TagScript.run( TagScript.java :250) at org.apache.commons.jelly.impl.ScriptBlock.run( ScriptBlock.java :95) at org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag ( MavenGoalTag.java:82) at org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction.performAction (MavenGoalTag.java
[m1.1] Unable to deploy to remote repository
Hi, I have been using maven 1.0.2 for more than a year now. I use it to make all of our releases on our internal repository. I have setup maven-proxy to access that repository and eveything works fine. In my build.properties file I have the following settings: maven.repo.RF1=sftp://gdps maven.repo.RF1.username=cvs maven.repo.RF1.password=*** maven.repo.RF1.directory=/cvs/maven/repo-local I tried to migrate to maven 1.1-beta3-SNAPSHOT (20060723) and I am unable to deploy something to the remote repository. (I tried jar:deploy, plugin:repository-deploy, etc all with the same exception). My configuration seems ok based on the maven-artifact-plugin doc. Looking on google I saw that we need to put the trust attribute to true, (if it is the ant task that is used by maven), but didn't find any way to configure it. I absolutely have to use sftp or scp. Here is the complete exception trace: Failed to deploy to: RF1 Reason: org.apache.maven.wagon.authentication.AuthenticationException: Cannot connect. Reason: reject HostKey: gdps org.apache.maven.wagon.authentication.AuthenticationException: Cannot connect. Reason: reject HostKey: gdps at org.apache.maven.wagon.providers.ssh.AbstractSshWagon.openConnection( AbstractSshWagon.java:232) at org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java :143) at org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java :106) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deployFiles( DefaultArtifactDeployer.java:372) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.doDeploy( DefaultArtifactDeployer.java:320) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.handleDeploy( DefaultArtifactDeployer.java:119) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy (DefaultArtifactDeployer.java:90) at org.apache.maven.artifact.deployer.DeployBean.deploy( DeployBean.java:155) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke( NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke( DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.commons.jelly.impl.DynamicBeanTag.doTag( DynamicBeanTag.java:180) at org.apache.commons.jelly.impl.StaticTagScript.run( StaticTagScript.java:102) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java :95) at org.apache.commons.jelly.impl.DynamicTag.doTag(DynamicTag.java :79) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:250) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java :95) at org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag( MavenGoalTag.java:82) at org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction.performAction (MavenGoalTag.java:115) at org.apache.maven.werkz.Goal.fire(Goal.java:647) at org.apache.maven.werkz.Goal.attain(Goal.java:582) at org.apache.maven.plugin.PluginManager.attainGoals( PluginManager.java:709) at org.apache.maven.MavenSession.attainGoals(MavenSession.java:264) at org.apache.maven.cli.App.doMain(App.java:546) at org.apache.maven.cli.App.main(App.java:1359) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke( NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke( DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.werken.forehead.Forehead.run(Forehead.java:551) at com.werken.forehead.Forehead.main(Forehead.java:581) Caused by: com.jcraft.jsch.JSchException: reject HostKey: gdps at com.jcraft.jsch.Session.checkHost(Unknown Source) at com.jcraft.jsch.Session.connect(Unknown Source) at com.jcraft.jsch.Session.connect(Unknown Source) at org.apache.maven.wagon.providers.ssh.AbstractSshWagon.openConnection( AbstractSshWagon.java:221) ... 31 more Thanks, Daniel
Re: Findbugs: java.lang.OutOfMemoryError: Java heap space
This is what I had to set to prevent all errors when building the site with a lot of reports MAVEN_OPTS= -Xmx1024m -Xms1024m -XX:MaxPermSize=512m I don't think the values need to be that high, but I think it is important to increase the MaxPermSize which is 32M by default I think On 2/10/06, M.-Leander Reimer [EMAIL PROTECTED] wrote: I had the same problem. However, increasing the memory via MAVEN_OPTS didn't help at all. Then I tried setting the findbugs plugin variable maven.findbugs.jvmargs=-Xmx512m but that didn't help either. In the end I upgraded from plugin version 1.0 to version 1.1 and the out of memory error disappeared. So try that. Leander Brian Burridge schrieb: I've tried 512, and that's all the memory I have on this laptop. Would it really require more than that for one report? I only have the findbugs report running in my pom right now. Brian On 2/10/06, Jeff Jensen [EMAIL PROTECTED] wrote: Perhaps set that value higher? Quoting Brian Burridge [EMAIL PROTECTED]: When I run the findbugs plugin I a getting an out of memory error: java heap sapce. I have set MAVEN_OPTS=-Xmx400m Is there something else I should set as well? Brian - 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 to take back-up and restore the postgresql database?? using maven
Hi, It is quite easy to backup a database using DBUnit in java. So I gues you would have to create a plugin to best achieve it. But the steps you will need to execute are: create a new DatabaseConnection object. (note the use of the public schema for postgresql when the tables are not in a specific schema) Something like: java.lang.Class.forName(org.postgresql.Driver); java.sql.Connection jdbcConnection = DriverManager.getConnection (jdbc:postgresql://localhost:5432/database, postgres, postgres); DatabaseConnection databaseConnection = new DatabaseConnection(jdbcConnection, public); Create the dataSet of the data to backup (can use complex queries to filter data) and write it in a file. The XmlDataSet format is hard to read compared to FlatXmlDataSet but is better to handle null values. QueryDataSet dataSet = new QueryDataSet(databaseConnection); dataSet.addTable(table1); dataSet.addTable(table2); dataSet.addTable(table3, select * from table3 where xxx 5000); XmlDataSet.write(dataSet, new FileOutputStream(C:/tmp/dataSet.xml)); Then re-import the data when it is done XmlDataSet dataSet2 = new XmlDataSet(new FileInputStream(C:/tmp/dataSet.xml)); DatabaseOperation.CLEAN_INSERT.execute(databaseConnection, dataSet2); Hope it can help Daniel On 12/7/05, Charles A [EMAIL PROTECTED] wrote: Hi All, I'm using Hibernate and Postgresql DB in our project. Now my maven script creating .War file. But problem is i have to take back-up and delete my database before run the maven script and restore the back-up database, once new database has created. I have checked DBUNIT and ddlutils site, but i didn't get clear idea where to start? and how to proceed? Thanks in advance Thanks Regards Charles
Re: How to take back-up and restore the postgresql database?? using maven
You may be able to do it in maven.xml with jelly scripting. But I guess it woulde be a lot easier to develop your own plugin. I havan't had to develop one myself so far so I cannot really give you advices on how to do it. You should use the JDBC driver provided by the PostgeSQL team for the specific version of the database you have installed. On 12/7/05, charles Anto [EMAIL PROTECTED] wrote: Many thanx daniel. How can i integrate these code with maven scripts. which driver i shd use postgresql or jdbc...? should i declear following code in the project.properties file? java.lang.Class.forName(org.postgresql.Driver); java.sql.Connection jdbcConnection = DriverManager.getConnection (jdbc:postgresql://localhost:5432/database, postgres, postgres); DatabaseConnection databaseConnection = new DatabaseConnection(jdbcConnection, public); Thanks Regards Charles On 12/7/05, Daniel Beland [EMAIL PROTECTED] wrote: Hi, It is quite easy to backup a database using DBUnit in java. So I gues you would have to create a plugin to best achieve it. But the steps you will need to execute are: create a new DatabaseConnection object. (note the use of the public schema for postgresql when the tables are not in a specific schema) Something like: java.lang.Class.forName(org.postgresql.Driver); java.sql.Connection jdbcConnection = DriverManager.getConnection (jdbc:postgresql://localhost:5432/database, postgres, postgres); DatabaseConnection databaseConnection = new DatabaseConnection(jdbcConnection, public); Create the dataSet of the data to backup (can use complex queries to filter data) and write it in a file. The XmlDataSet format is hard to read compared to FlatXmlDataSet but is better to handle null values. QueryDataSet dataSet = new QueryDataSet(databaseConnection); dataSet.addTable(table1); dataSet.addTable(table2); dataSet.addTable(table3, select * from table3 where xxx 5000); XmlDataSet.write(dataSet, new FileOutputStream(C:/tmp/dataSet.xml)); Then re-import the data when it is done XmlDataSet dataSet2 = new XmlDataSet(new FileInputStream(C:/tmp/dataSet.xml)); DatabaseOperation.CLEAN_INSERT.execute(databaseConnection, dataSet2); Hope it can help Daniel On 12/7/05, Charles A [EMAIL PROTECTED] wrote: Hi All, I'm using Hibernate and Postgresql DB in our project. Now my maven script creating .War file. But problem is i have to take back-up and delete my database before run the maven script and restore the back-up database, once new database has created. I have checked DBUNIT and ddlutils site, but i didn't get clear idea where to start? and how to proceed? Thanks in advance Thanks Regards Charles
Re: Help! - maven-proxy encountered NTLM authentication problem
Hi, I had the same problem, and recompiled it using NTCredentials instead and adding an attribute in the properties file proxy.one.domain=XXX I can send you the compiled jar by email if you wish? Daniel On 11/22/05, Law Green-A20134 [EMAIL PROTECTED] wrote: Hi, my maven-proxy.properties file has configured proxy server as follows: proxy.one.host=proxy_server proxy.one.port=1080 proxy.one.username=user proxy.one.password=password Unfortunately, the maven-proxy console report the following error while maven start download from central repository: 2005-11-22 17:45:38,937 [WARN ] commons.httpclient.HttpMethodBase - Credentials cannot be used for NTLM authentication: org.apache.commons.httpclient.UsernameP asswordCredentials 2005-11-22 17:45:38,937 [INFO ] proxy.config.HttpRepoConfiguration - Repo[www-i biblio-org]: Unable to find http://www.ibiblio.org/maven2/org/apache/maven/plugi http://www.ibiblio.org/maven2/org/apache/maven/plugi ns/maven-metadata.xml because of [407] = Proxy Authentication Required Anyone has a clue for solution? Thanks and Best Regards, Green Law --- Software Center Motorola China Global Software Group Phone: 86-28-87826088-2253 Email: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] IM: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] Jabber: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] --- Message Classification: Motorola Confidential Proprietary Motorola Internal Use only Motorola General Business Information
Re: Help! - maven-proxy encountered NTLM authentication problem
Just found out that tool though! http://ntlmaps.sourceforge.net/ You may want to give it a try as it can be used in all your applications! On 11/23/05, Daniel Beland [EMAIL PROTECTED] wrote: Hi, I had the same problem, and recompiled it using NTCredentials instead and adding an attribute in the properties file proxy.one.domain=XXX I can send you the compiled jar by email if you wish? Daniel On 11/22/05, Law Green-A20134 [EMAIL PROTECTED] wrote: Hi, my maven-proxy.properties file has configured proxy server as follows: proxy.one.host=proxy_server proxy.one.port=1080 proxy.one.username=user proxy.one.password=password Unfortunately, the maven-proxy console report the following error while maven start download from central repository: 2005-11-22 17:45:38,937 [WARN ] commons.httpclient.HttpMethodBase - Credentials cannot be used for NTLM authentication: org.apache.commons.httpclient.UsernameP asswordCredentials 2005-11-22 17:45:38,937 [INFO ] proxy.config.HttpRepoConfiguration - Repo[www-i biblio-org]: Unable to find http://www.ibiblio.org/maven2/org/apache/maven/plugi http://www.ibiblio.org/maven2/org/apache/maven/plugi ns/maven-metadata.xml because of [407] = Proxy Authentication Required Anyone has a clue for solution? Thanks and Best Regards, Green Law --- Software Center Motorola China Global Software Group Phone: 86-28-87826088-2253 Email: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] IM: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] Jabber: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] --- Message Classification: Motorola Confidential Proprietary Motorola Internal Use only Motorola General Business Information
Re: Changelog returns 0 entries
Hi,
I have the exact same problem, so I kept on using 1.7.2.
But I really want the new functionalities of 1.8.2 (tag or date
types), and since no one answered your post I tried to find the
problem and finally got it after a lot of diff viewing in the
changelog viewcvs.
It seems they changed the code in 1.8.1 to put quotes around the dates
on windows for users using cvsnt.
(http://jira.codehaus.org/browse/MPCHANGELOG-47)
if ( System.getProperty( os.name ).startsWith( Windows ) )
{
cmd = \ + cmd + \;
}
return -d + cmd;
But they never considered users on windows using either cygwin's cvs
or the GNU cvs for DOS.
So as a workaround you can change the os.name java property but I
don`t guarantee that it will not affect the other plugins (maven
-Dos.name=none maven-changelog-plugin:report)
I opened a bug in jira (http://jira.codehaus.org/browse/MPCHANGELOG-69)
Daniel
On 8/2/05, Jan Tanis [EMAIL PROTECTED] wrote:
Hello,
I recently started using Maven. I want it to autogenerate reports on our
repositories. I installend Maven 1.0.2. Brett told me to upgrade the
changelog plugin, so I did. It does call the CVS server but it will
alway return 0 entries. When I manual run the log with the following
command - C:\coat\workspace\cocoscvs log -d 2005-07-032005-08-03 it
returns 100dreds of entries.
Following is a part of the debug output of -
C:\coat\workspace\cocosmaven -X maven-changelog-plugin:report
maven-changelog-plugin:report:
[echo] Generating the changelog report
Executing CVS command: log -d 2005-07-032005-08-03
ChangeSet between 2005-07-03 and 2005-08-03: 0 entries
attaining goal build:end
popping off [EMAIL PROTECTED] for
[EMAIL PROTECTED] in
maven-xdoc-plugin:maven-xdoc-plugin
popping off [EMAIL PROTECTED] for
[EMAIL PROTECTED] in
maven-pom-plugin:maven-pom-plugin
popping off [EMAIL PROTECTED] for
[EMAIL PROTECTED] in
maven-changelog-plugin:maven-changelog-plugin
popping off [EMAIL PROTECTED] for
[EMAIL PROTECTED] in
maven-artifact-plugin:maven-artifact-plugin
popping off [EMAIL PROTECTED] for
[EMAIL PROTECTED] in cocos:cocos
BUILD SUCCESSFUL
Final Memory: 3M/5M
Total time: 3 seconds
Finished at: Tue Aug 02 08:45:53 CEST 2005
--
Met Vriendelijke Groet/Kindest Regards
Jan Tanis (mailto:[EMAIL PROTECTED])
COAS The Netherlands
-
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]
