Re: maven appends sub-project artifactId to urls - Please help - design suggestion
/The maven inheritance mechanism will not take the parent pom into
consideration
/The main idea was to change the hard-coded rule always append
artifactId to implicit urls to something
configurable and located in the super pom. Only if somebody wanted to
change the 'rule' that could be
achieved with a minor effort of two intermediary poms.
Yes, this will require a change of the inheritance mechanism. I'm not
familiar with Maven internals
(at least not yet). However, I presumed the inheritance logic was
located to a single place and therefore
could be changed according to my suggestion with a minor effort. Please,
forgive me if my suggestion
turns out to be major implementation headache.
Best regards,
/jens
VUB Stefan Seidel skrev:
Jens Riboe wrote:
As I understand it; the current rule implements implicit URLs as
${parent.url}/${project.artifactId}
For example:
scm
connection${parentPOM.scm.connection}/${project.artifactId}/connection
...
/scm
Where parentPOM is a made-up symbol denoting an upward search for the
pom property that follows (scm.connection).
So, how about the following suggestion:
The Super POM contains this kind of definition for all URLs where
this rule applies today. When the effective POM
is computed for a sub-project it uses the closest url definition
that contains the symbol parentPOM. If none is
found expect the def in super pom, this one is used and the rule
applies as it always has.
This will break existing builds.
The maven inheritance mechanism will not take the parent pom into
consideration if you say something like
connectionscm:cvs:[EMAIL PROTECTED]:/yyy/connection
because this is considered as a fixed string and thus overrides the
value from the parent. Maven only inherits values from parent POMs
when the tags are non-existing in the child pom or in special cases
likes plugin configurations from pluginManagement or plugin executions
with the same id.
Stefan
maven appends sub-project artifactId to urls - Please help
I have an organization POM, with common defs, including url templates
for scm and distribution.
Here are the relevant snippets, from the parent pom
scm
connectionscm:svn:https://www.myhost.com/svn/pub/${project.name}/trunk/connection
developerConnectionscm:svn:https://www.myhost.com/svn/pub/${project.name}/trunk/developerConnection
urlhttp://www.myhost.com/websvn/${project.name}/trunk/url
/scm
site
iddoc/id
urldav:http://dav.myhost.com:8000/doc/${project.name}//url
/site
Here are the relevant snippets, from a test sub-pom
parent
...
/parent
artifactIdhello/artifactId
version0.17/version
packagingjar/packaging
nameHelloMvn/name
The problem is that the URLs of the effective pom of the sub-project has the
artifactId appended.
scm
connectionscm:svn:https://www.myhost.com/svn/pub/HelloMvn/trunk/hello/connection
developerConnectionscm:svn:https://www.myhost.com/svn/pub/HelloMvn/trunk/hello/developerConnection
urlhttp://www.myhost.com/websvn/HelloMvn/trunk/hello/url
/scm
site
iddoc/id
urldav:http://dav.myhost.com:8000/doc/HelloMvn/hello/url
/site
So my question is: How can I disable this feature, or configure the way it is
working?
As it stands right now, I consider this feature to be a bug. It's not
documented and I hardly see the benefit of it.
There was a mail trail touching this back in December, but it didn't come to a
conclusion
http://www.mail-archive.com/users@maven.apache.org/msg77123.html
Regards,
/jens
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven appends sub-project artifactId to urls - Please help - design suggestion
As I understand it; the current rule implements implicit URLs as
${parent.url}/${project.artifactId}
For example:
scm
connection${parentPOM.scm.connection}/${project.artifactId}/connection
...
/scm
Where parentPOM is a made-up symbol denoting an upward search for the
pom property that follows (scm.connection).
So, how about the following suggestion:
The Super POM contains this kind of definition for all URLs where this
rule applies today. When the effective POM
is computed for a sub-project it uses the closest url definition that
contains the symbol parentPOM. If none is
found expect the def in super pom, this one is used and the rule applies
as it always has.
On the other hand, if one decides to put an url expression containing
parentPOM into a POM of type 'pom',
then there is a new definition and will be used. That means, we have a
way to define how sub-project urls should
be constructed. I would be delighted if I could define an expression as
${parentPOM.scm.connection}/${project.name}/trunk
There is a residual problem, however: I cannot define both an url
expansion expression and an actual url expression
that is intended to be used in sub-projects. The easiest solution, is
just to have two organization poms, the top-most
pom contains the url expansion expressions (overriding the rule from the
super pom) and the one beneath is the
original org pom, containing actual urls that will be used in the
expansions further down.
I'm convinced there are other more elegant solutions. However, the
suggestion above would be fairly easy to implement
without breaking existing code and poms (or require a POM version
increment), but still provide a way for org-pom
designers to tweak the url expansions the way they want.
Comments / Objections ???
Cheers,
Jens
VUB Stefan Seidel skrev:
I agree, it is a bit too late to change this behaviour now. Maybe some
other suffix like $ or ${fixed} or you-name-it could be the cure. Then
all existing builds would continue to work and if someone would not
want the artifact id appended, they can add the special character.
Stefan
Brian E. Fox wrote:
The discussion in the issue revolves around the fact that changing this
behavior to as documented will break every build where there isn't a /
at the end. It's not apparent how to fix this without hosing tons of
unsuspecting users.
--Brian
-Original Message-
From: VUB Stefan Seidel [mailto:[EMAIL PROTECTED] Sent: Thursday,
February 21, 2008 6:03 AM
To: Maven Users List
Subject: Re: maven appends sub-project artifactId to urls - Please help
I added a comment to http://jira.codehaus.org/browse/MNG-3244.
You may want to add you votes. Apparently, it was originally planned
to not append the artifact id unless the URL would end with a /.
Stefan
Ben Lidgey wrote:
-Original Message-
From: VUB Stefan Seidel [mailto:[EMAIL PROTECTED]
Sent: 21 February 2008 09:52
To: Maven Users List
Subject: Re: maven appends sub-project artifactId to urls -
Please help
Hi Jens,
you are complaining about an essential feature of maven.
Having maven automatically extend the urls, scm urls, site
urls etc. with the list of parent artifact ids is crucial for
multi-module projects. No-one would want to enter this
information again and again through several levels of child
modules which are hosted within a common directory tree. I
agree that the docs are not clear about it, at least I
couldn't find it documented. I see your point, and there are
other problems, like when the directory name of a sub-module
is not equal to the artifact id, but in general it is an
important feature.
How to disable - I don't know. Maybe you will need to file
two things in
JIRA: a documentation request and a feature request to disable it.
HTH,
Stefan
We have a similar problem to Jens as our projects are structured in
Eclipse friendly structure, e.g.
ParentProject
- pom.xml
ChildProject1
- pom.xml
- src/java etc
ChildProject2
- pom.xml
- src/java etc
Which is different to the standard Maven dir structure, e.g.
ParentProject
- pom.xml
- ChildProject1
- pom.xml
- src/java etc
- ChildProject2
- pom.xml
- src/java etc
It would make sense to me to be able to specify a different naming
strategy, perhaps the Maven one is used as a default, but you could
define a different naming strategy and set that to be used instead, e.g.
scm namingStrategy=org.apache.maven.scm.FlatTreeNamingStrategy
...
/scm
That doesn't append artifactIds. Then if people had other weird and
whacky ways of structuring projects they could write custom naming
strategies to behave in accordance with their structures.
Ben
This e-mail is confidential and intended solely for the use of the
individual(s) to whom it is addressed. Any views or opinions expressed
are those of the author. If you are not the intended recipient, please
be advised that any use, dissemination, printing or copying of this
email is strictly prohibited.
Re: problem with svn via https - pls help
Continuum use the command line to launch svn so if svn command works fine with the tomcat user, it should work too from Continuum. That's my thought too. So, where do you suggest me looking when it doesn't? from the log I can see it executes /bin/sh -c cd /var/cache/tomcat/continuum/work svn --non-interactive checkout https://www.ribomation.com/svn/pub/DateCalc/trunk 2 [EMAIL PROTECTED] runs as user tomcat logged on as the same user, I can checkout using svn co ... I got around it by removing the HTTPS requirement for my svn repo (accessed internally). However, that's less than ideal for obvious reasons. Emmanuel Venisse skrev: Continuum use the command line to launch svn so if svn command works fine with the tomcat user, it should work too from Continuum. Emmanuel On Feb 19, 2008 8:02 PM, Jens Riboe [EMAIL PROTECTED] wrote: I have problem with Continuum not not being able to checkout from svn via https, because of a SSL cert validation error. Provider message: The svn command failed. Command output: --- svn: PROPFIND request failed on '/svn/pub/DateCalc/trunk' svn: PROPFIND of '/svn/pub/DateCalc/trunk': Server certificate verification failed: issuer is not trusted (https://www.ribomation.com) --- However, I can sucessfully checkout using either of svn co https://... mvn scm:checkout the .subversion/servers file contains certs defs (CA + SSL cert) ssl-authority-files = /etc/certs/ribomation_com.crt.pem;/etc/certs/www_ribomation_com.crt.pem Continumm is running at * Tomcat 6.0.14 * Java 1.6.0_03-b05 * Ubuntu Server 7.19 (2.6.22-14/i386) Tomcat runs as user 'tomcat' and the checkout commands above is performed using that user in its home dir So, my question is: What is the key difference of how Continuum handles svn (under user tomcat) and a user 'tomcat' doing checkouts directly? Do Continuum SCM/svn uses the settings in ~/.subversion? Where else should I look for a configuration of svn, for usage by Continuum? Here is a log snippet, showing Continuum uses svn within a shell cmd: 187758 [pool-1-thread-1] INFO org.apache.maven.continuum.scm.ContinuumScm:default - Checking out project: 'DateCalc', id: '2' to '/var/cache/tomcat/continuum/work/2'. 187783 [pool-1-thread-1] INFO org.apache.maven.scm.manager.ScmManager:default - Executing: /bin/sh -c cd /var/cache/tomcat/continuum/work svn --non-interactive checkout https://www.ribomation.com/svn/pub/DateCalc/trunk 2 187784 [pool-1-thread-1] INFO org.apache.maven.scm.manager.ScmManager:default - Working directory: /var/cache/tomcat/continuum/work 187897 [pool-1-thread-1] WARN org.apache.maven.continuum.scm.ContinuumScm:default - Error while checking out the code for project: 'DateCalc', id: '2' to '/var/cache/tomcat/continuum/work/2'. 187897 [pool-1-thread-1] WARN org.apache.maven.continuum.scm.ContinuumScm:default - Command output: svn: PROPFIND request failed on '/svn/pub/DateCalc/trunk' svn: PROPFIND of '/svn/pub/DateCalc/trunk': Server certificate verification failed: issuer is not trusted (https://www.ribomation.com) 187897 [pool-1-thread-1] WARN org.apache.maven.continuum.scm.ContinuumScm:default - Provider message: The svn command failed. Thanks /jens
Re: problem with svn via https - pls help
OK. Thanks anyway. I could carry on with plain http access. /jens Emmanuel Venisse skrev: I'm sorry, but for the moment, I don't have ideas about it. Emmanuel On Feb 19, 2008 11:00 PM, Jens Riboe [EMAIL PROTECTED] wrote: Continuum use the command line to launch svn so if svn command works fine with the tomcat user, it should work too from Continuum. That's my thought too. So, where do you suggest me looking when it doesn't? from the log I can see it executes /bin/sh -c cd /var/cache/tomcat/continuum/work svn --non-interactive checkout https://www.ribomation.com/svn/pub/DateCalc/trunk 2 [EMAIL PROTECTED] runs as user tomcat logged on as the same user, I can checkout using svn co ... I got around it by removing the HTTPS requirement for my svn repo (accessed internally). However, that's less than ideal for obvious reasons. Emmanuel Venisse skrev: Continuum use the command line to launch svn so if svn command works fine with the tomcat user, it should work too from Continuum. Emmanuel On Feb 19, 2008 8:02 PM, Jens Riboe [EMAIL PROTECTED] wrote: I have problem with Continuum not not being able to checkout from svn via https, because of a SSL cert validation error. Provider message: The svn command failed. Command output: --- svn: PROPFIND request failed on '/svn/pub/DateCalc/trunk' svn: PROPFIND of '/svn/pub/DateCalc/trunk': Server certificate verification failed: issuer is not trusted (https://www.ribomation.com) --- However, I can sucessfully checkout using either of svn co https://... mvn scm:checkout the .subversion/servers file contains certs defs (CA + SSL cert) ssl-authority-files = /etc/certs/ribomation_com.crt.pem;/etc/certs/www_ribomation_com.crt.pem Continumm is running at * Tomcat 6.0.14 * Java 1.6.0_03-b05 * Ubuntu Server 7.19 (2.6.22-14/i386) Tomcat runs as user 'tomcat' and the checkout commands above is performed using that user in its home dir So, my question is: What is the key difference of how Continuum handles svn (under user tomcat) and a user 'tomcat' doing checkouts directly? Do Continuum SCM/svn uses the settings in ~/.subversion? Where else should I look for a configuration of svn, for usage by Continuum? Here is a log snippet, showing Continuum uses svn within a shell cmd: 187758 [pool-1-thread-1] INFO org.apache.maven.continuum.scm.ContinuumScm:default - Checking out project: 'DateCalc', id: '2' to '/var/cache/tomcat/continuum/work/2'. 187783 [pool-1-thread-1] INFO org.apache.maven.scm.manager.ScmManager:default - Executing: /bin/sh -c cd /var/cache/tomcat/continuum/work svn --non-interactive checkout https://www.ribomation.com/svn/pub/DateCalc/trunk 2 187784 [pool-1-thread-1] INFO org.apache.maven.scm.manager.ScmManager:default - Working directory: /var/cache/tomcat/continuum/work 187897 [pool-1-thread-1] WARN org.apache.maven.continuum.scm.ContinuumScm:default - Error while checking out the code for project: 'DateCalc', id: '2' to '/var/cache/tomcat/continuum/work/2'. 187897 [pool-1-thread-1] WARN org.apache.maven.continuum.scm.ContinuumScm:default - Command output: svn: PROPFIND request failed on '/svn/pub/DateCalc/trunk' svn: PROPFIND of '/svn/pub/DateCalc/trunk': Server certificate verification failed: issuer is not trusted (https://www.ribomation.com) 187897 [pool-1-thread-1] WARN org.apache.maven.continuum.scm.ContinuumScm:default - Provider message: The svn command failed. Thanks /jens
problem with svn via https - pls help
I have problem with Continuum not not being able to checkout from svn via https, because of a SSL cert validation error. Provider message: The svn command failed. Command output: --- svn: PROPFIND request failed on '/svn/pub/DateCalc/trunk' svn: PROPFIND of '/svn/pub/DateCalc/trunk': Server certificate verification failed: issuer is not trusted (https://www.ribomation.com) --- However, I can sucessfully checkout using either of svn co https://... mvn scm:checkout the .subversion/servers file contains certs defs (CA + SSL cert) ssl-authority-files = /etc/certs/ribomation_com.crt.pem;/etc/certs/www_ribomation_com.crt.pem Continumm is running at * Tomcat 6.0.14 * Java 1.6.0_03-b05 * Ubuntu Server 7.19 (2.6.22-14/i386) Tomcat runs as user 'tomcat' and the checkout commands above is performed using that user in its home dir So, my question is: What is the key difference of how Continuum handles svn (under user tomcat) and a user 'tomcat' doing checkouts directly? Do Continuum SCM/svn uses the settings in ~/.subversion? Where else should I look for a configuration of svn, for usage by Continuum? Here is a log snippet, showing Continuum uses svn within a shell cmd: 187758 [pool-1-thread-1] INFO org.apache.maven.continuum.scm.ContinuumScm:default - Checking out project: 'DateCalc', id: '2' to '/var/cache/tomcat/continuum/work/2'. 187783 [pool-1-thread-1] INFO org.apache.maven.scm.manager.ScmManager:default - Executing: /bin/sh -c cd /var/cache/tomcat/continuum/work svn --non-interactive checkout https://www.ribomation.com/svn/pub/DateCalc/trunk 2 187784 [pool-1-thread-1] INFO org.apache.maven.scm.manager.ScmManager:default - Working directory: /var/cache/tomcat/continuum/work 187897 [pool-1-thread-1] WARN org.apache.maven.continuum.scm.ContinuumScm:default - Error while checking out the code for project: 'DateCalc', id: '2' to '/var/cache/tomcat/continuum/work/2'. 187897 [pool-1-thread-1] WARN org.apache.maven.continuum.scm.ContinuumScm:default - Command output: svn: PROPFIND request failed on '/svn/pub/DateCalc/trunk' svn: PROPFIND of '/svn/pub/DateCalc/trunk': Server certificate verification failed: issuer is not trusted (https://www.ribomation.com) 187897 [pool-1-thread-1] WARN org.apache.maven.continuum.scm.ContinuumScm:default - Provider message: The svn command failed. Thanks /jens
maven appends sub-project artifactId to urls
I have an organization POM, with common defs, including url templates
for scm and distribution.
Here are the relevant snippets, from the parent pom
scm
connectionscm:svn:https://www.ribomation.com/svn/pub/${project.name}/trunk/connection
developerConnectionscm:svn:https://www.ribomation.com/svn/pub/${project.name}/trunk/developerConnection
urlhttp://www.ribomation.com/websvn/${project.name}/trunk/url
/scm
site
idriboutils/id
urldav:http://dav.ribomation.com:8000/doc/${project.name}//url
/site
The problem is that these URLs of the effective pom of projects using
the parent-pom,
has the artifactId appended. Here are the relevant snippets, from a test pom
parent
...
/parent
artifactIdhello/artifactId
version0.17/version
packagingjar/packaging
nameHelloMvn/name
scm
connectionscm:svn:https://www.ribomation.com/svn/pub/HelloMvn/trunk/hello/connection
developerConnectionscm:svn:https://www.ribomation.com/svn/pub/HelloMvn/trunk/hello/developerConnection
urlhttp://www.ribomation.com/websvn/HelloMvn/trunk/hello/url
/scm
site
idriboutils/id
urldav:http://dav.ribomation.com:8000/doc/HelloMvn/hello/url
/site
So my question is: How can I disable this feature, or configure the way
it is working?
As it stands right now, I consider this feature to be a bug. It's not
documented and I hardly see the benefit of it.
There was a mail trail touching this back in December, but it didn't
come to a conclusion
http://www.mail-archive.com/users@maven.apache.org/msg77123.html
Regards,
/jens
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cannot deploy to [EMAIL PROTECTED]
I cannot deploy to archiva running at tomcat. I'm getting this error 2008-feb-12 20:00:21 org.apache.commons.httpclient.HttpMethodBase processRedirectResponse INFO: Redirect requested but followRedirects is disabled Another person seems to have asked the same question, but without an answer http://mail-archives.apache.org/mod_mbox/maven-archiva-users/200801.mbox/browser My platform: Archiva WAR 1.0 Tomcat 6.0.14 Java 1.6.0_03-b05 Ubuntu Server 7.10 Any insights into this problem and its resolution are highly welcome. /jens
Re: cannot deploy to [EMAIL PROTECTED]
What command are you using to deploy? mvn deploy distributionManagement section of your pom look like distributionManagement repository idmy-public/id urldav:http://host:8080/archiva/repository/pub//url /repository snapshotRepository idmy-snapshot/id urldav:http://host:8080/archiva/repository/snapshot//url /snapshotRepository /distributionManagement granted the repository manager role for the repo you're trying to deploy to yes. the user 'deployer' has roles Repository Manager - snapshot, Repository Manager - pub, ... How have you configured credentials in settings.xml yes. server idmy-public/id usernamedeployer/username password.../password /server server idmy-snapshot/id usernamedeployer/username password.../password /server click on 'Permalink (Message view)' http://mail-archives.apache.org/mod_mbox/maven-archiva-users/200801.mbox/[EMAIL PROTECTED] this can be a tomcat related problem. I'm getting google hits on that error message, but nothing that really nails down the problem. any light on this problem is appreciated /jens Wendy Smoak skrev: On Feb 12, 2008 12:26 PM, Jens Riboe [EMAIL PROTECTED] wrote: I cannot deploy to archiva running at tomcat. I'm getting this error 2008-feb-12 20:00:21 org.apache.commons.httpclient.HttpMethodBase processRedirectResponse INFO: Redirect requested but followRedirects is disabled There isn't enough information here to be able to guess what's wrong. What command are you using to deploy? If 'mvn deploy', what does the distributionManagement section of your pom look like? Have you granted the repository manager role for the repo you're trying to deploy to? How have you configured credentials in settings.xml? Another person seems to have asked the same question, but without an answer http://mail-archives.apache.org/mod_mbox/maven-archiva-users/200801.mbox/browser Unfortunately that's a link to the entire January archive. When you're viewing the message, click on 'Permalink (Message view)' and then paste that url.
[m2] Need help: How to managing the version number in a multi-module project
Background: I have a typical multi-module project, with a parent pom and a handful of child poms inheriting from the parent. The parent pom contains the version, which is inherited to the child poms, which affect all generated child artifacts. So far so good. Problem: However, the parent pom is referred by version from each child pom, which causes a slight maintenance problem when it's time to change the version number. Parent POM groupIdggg/groupId artifactIdaaa/artifactId version1.0.3/version packagingpom/packaging Child POMs parent groupIdggg/groupId artifactIdaaa/artifactId version1.0.3/version /parent artifactIdccc/artifactId packagingjar/packaging I have to update the version number in the parent pom, as well as all references to the parent in each child pom. Clearly, this is clumsy. AFAIK the version number of the parent must be present in the child pom. Question: So, what are the best practices for this problem? Bi-condition: I'm working mostly off-line, so the release plug-in (using a SNAPSHOT version) is not appropriate in my case. Many thanks in advance for any tips, /Jens - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [m2] Need help: How to managing the version number in a multi-module
However we are using the M2 Release plugin to handle your maintenance problem. AFAIK this plugin requires me to be online (access to SVN repo). In my case I'm mostly on the move working off-line. Regards, /Jens -Original Message- From: Jorgen Fastrup [mailto:[EMAIL PROTECTED] Sent: 04 August 2006 14:47 To: users@maven.apache.org Subject: Re: [m2] Need help: How to managing the version number in a multi-module Hi Jens I'm not aware of what is considered best pratice on this matter. However we are using the M2 Release plugin to handle your maintenance problem. Eache single project included in our multiproject structure uses the version1.0-SNAPSHOT/version tag. Once we cut a new release for the multiproject we execute the M2 Release plugin. The plugin - among other things - assigns a new identical version tag to each POM located in the multiproject structure and thus the version integrity of the entire multiproject is preserved. Regards Jorgen Regards Jorgen -- View this message in context: http://www.nabble.com/-m2--Need-help%3A-How-to-managing-the-version-numb er-in-a-multi-module-project-tf2050906.html#a5649632 Sent from the Maven - Users forum 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]
[M2] Application version in multi-module project
Background: I have a typical multi-module project, with a parent pom and a handful of child poms inheriting from the parent. The parent pom contains the version, which is inherited to the child poms, which affect all generated child artifacts. So far so good. Problem: However, the parent pom is referred by version from each child pom, which causes a slight maintenance problem when it's time to change the version number. I have to update the version number in the parent pom, as well as all references to the parent in each child pom. Clearly, this is clumsy. AFAIK the version number of the parent must be present in the child pom. Question: So, what are the best practices for this problem? Bi-condition: I'm working mostly off-line, so the release plug-in is not appropriate in my case. Many thanks in advance for any tips, /Jens - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [m2] buildnumber-plugin
org.codehaus.mojo:maven-buildnumber-plugin
I couldn't find it at codehaus (http://mojo.codehaus.org/).
Do you know where I can get more info about it?
/Jens
-Original Message-
From: Christian Wiesing [mailto:[EMAIL PROTECTED]
Sent: 01 June 2006 14:43
To: Maven Users List
Subject: Re: [m2] buildnumber-plugin
Thanks.
It works great.
Thorsten Heit schrieb:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Christian,
i have a problem with the buildnumber-plugin. When i execute mvn
buildnumber:create I get the following error:
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] An error has occurred while checking scm status.
Embedded error: Can't load the scm provider.
The scm url cannot be null.
[INFO]
I had the same problem and fixed it by using the following plugin
configuration:
build
plugins
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdmaven-buildnumber-plugin/artifactId
version0.9.2-SNAPSHOT/version
configuration
format{0,number}/format
items
itembuildNumber0/item
/items
/configuration
executions
execution
goals
goalcreate/goal
/goals
/execution
/executions
/plugin
...
/build
HTH
Thorsten
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.3 (MingW32)
iD8DBQFEft7NQvObkgCcDe0RAlv/AKDdULFWUU4Yk+WpXcD1KvHSaSQMZQCgvZm8
w8QOUyU9aQmXb/G0MgnHzwA=
=IrRP
-END PGP SIGNATURE-
-
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]
RE: [M2] documentaion bundled with binaries ?
if HTML documentation can be bundled along with M2 binaries I think this is a very good suggestion! At least have access to the docs ZIP in an easy way. (I don't think must users consider svn export/mvn site easy ;-) /Jens -Original Message- From: Sharma, Jaikumar [mailto:[EMAIL PROTECTED] Sent: 07 April 2006 07:58 To: Maven Users List Subject: [M2] documentaion bundled with binaries ? Dear Maven users, It would be a plus for a M2 users, if HTML documentation can be bundled alogwith M2 binaries, becuase if someone is offline then he can still brainstorm things, by going through the proivided offline documentation! I am not sure, any one has raised this earlier! Regards, Jaikumar - - - - - - - DISCLAIMER- - - - - - - - Unless indicated otherwise, the information contained in this message is privileged and confidential, and is intended only for the use of the addressee(s) named above and others who have been specifically authorized to receive it. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this message and/or attachments is strictly prohibited. The company accepts no liability for any damage caused by any virus transmitted by this email. Furthermore, the company does not warrant a proper and complete transmission of this information, nor does it accept liablility for any delays. If you have received this message in error, please contact the sender and delete the message. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
How do I filter site.xml and APT docs?
I would like to put POM variables in the site docs, like site.xml and the APT files. How can I do that? I tried it, but it doesn't work out-of-the-box. Thanks in advance, /Jens - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Re: [M2] mvn site:deploy throws an exception
do know that FTP will most likely be a lot slower then ssh I'm in the process of setting up an internal server, which need to be accessed outside vpn but still be protected/restricted. There are two cases against ssh [1] The sysop don't like to create accounts for all potential users [2] I haven't succeeded with site:deploy using the windows/putty/scpexe combo (depends download and deploy upload works fine) The web part of the site is accessed by https/clientCerts, which is really good from both a security and usability point of view. However, to my knowledge neither https nor clientCerts are supported by mavan/wagon. I don't know about the status of the wagon DAV provider and if it eventually will support https with clientCerts. With ftp I have created a maven user with [a] restricted permissions [b] no login shell [c] chroot to its home dir and created the mvn repo and site dir there This gives an acceptable level of security and I can both download and upload. The last remaining task is to provide a way to perform site:deploy. It seems to me that the site:deploy implementation do not use the wagon providers in the same way as deploy:deploy. Maybe, have to advise the users to stick to plain old ftp upload for the site files. Comments and/or suggestions are highly welcome. /Jens -Original Message- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Geoffrey De Smet Sent: 30 March 2006 12:41 To: users@maven.apache.org Subject: Re: [M2] mvn site:deploy throws an exception I don't know, but I do know that FTP will most likely be a lot slower then ssh in practice: - ssh deploy creates one big zip, sends that and unzips it. - ftp sends file per file. Deploying my site manually with filezilla (multiple select) over ftp took me +1 hour. Maybe it doesn't use true multiple file sending? Deploying my site automatically with ssh-deploy took less then 10 minutes. Jens Riboe wrote: I'm trying to use FTP for site deployment, but get an exception. Is FTP supported, for site upload? C:\temp\nnnmvn -e site:deploy + Error stacktraces are turned on. [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'site'. [INFO] [INFO] Building Whatever [INFO]task-segment: [site:deploy] [INFO] [INFO] [site:deploy] [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Wagon protocol 'ftp' doesn't support directory copying [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Wagon protocol 'ftp' doesn't support directory copying at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default LifecycleExecutor.java:559) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoa l(DefaultLifecycleExecutor.java:488) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultL ifecycleExecutor.java:458) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle Failures(DefaultLifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments( DefaultLifecycleExecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec ycleExecutor.java:140) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.MojoExecutionException: Wagon protocol 'ftp' doesn't support directory copying at org.apache.maven.plugins.site.SiteDeployMojo.execute(SiteDeployMojo.java :120) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMa nager.java:412) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default LifecycleExecutor.java:534) ... 16 more [INFO
[M2] Is FTP maven2 repository supported?
I have succeed with FTP upload (deploy), but was surprised to find out that FTP download (repo/depends) failed. [WARNING] repository metadata for: 'artifact org.apache.maven.wagon:wagon-ftp' could not be retrieved from repository: myFTPsite due to an error: Unsupported Protocol: 'ftp': Cannot find wagon which supports the requested protocol: ftp Am I missing something? Or, is ftp m2 repo not supported? If not, will it be supported soon? Thanks for your help. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [M2] Is FTP maven2 repository supported?
It is supported but there some *undocumented* steps to perform, Will it be documented? I can give you the complete listing Yes, please! I have copied wagon-ftp-1.0-alpha-6.jar into the maven\lib, but I guess its transitive depend set need to be there as well? /Jens -Original Message- From: Alexandre Poitras [mailto:[EMAIL PROTECTED] Sent: 29 March 2006 13:21 To: Maven Users List Subject: Re: [M2] Is FTP maven2 repository supported? It is supported but there some *undocumented* steps to perform, ie copying some libs in maven\lib directory. I can give you the complete listing in like two hours once I am at my job. On 3/29/06, Jens Riboe [EMAIL PROTECTED] wrote: I have succeed with FTP upload (deploy), but was surprised to find out that FTP download (repo/depends) failed. [WARNING] repository metadata for: 'artifact org.apache.maven.wagon:wagon-ftp' could not be retrieved from repository: myFTPsite due to an error: Unsupported Protocol: 'ftp': Cannot find wagon which supports the requested protocol: ftp Am I missing something? Or, is ftp m2 repo not supported? If not, will it be supported soon? Thanks for your help. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Alexandre Poitras Québec, Canada - 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]
[M2] Is FTP maven2 site deploy supported?
I have FTP download (depends) and upload (deploy) working. /Thanks However, here's next problem: Is FTP supported for site:deploy? [INFO] [site:deploy] [INFO] Wagon protocol 'ftp' doesn't support directory copying Am I missing some additional setups? (I have distributionManagement/site configured in my pom) Thanks in advance, /jens -Original Message- From: Jens Riboe [mailto:[EMAIL PROTECTED] Sent: 29 March 2006 15:26 To: Maven Users List Cc: [EMAIL PROTECTED] Subject: RE: [M2] Is FTP maven2 repository supported? It is supported but there some *undocumented* steps to perform, Will it be documented? I can give you the complete listing Yes, please! I have copied wagon-ftp-1.0-alpha-6.jar into the maven\lib, but I guess its transitive depend set need to be there as well? /Jens -Original Message- From: Alexandre Poitras [mailto:[EMAIL PROTECTED] Sent: 29 March 2006 13:21 To: Maven Users List Subject: Re: [M2] Is FTP maven2 repository supported? It is supported but there some *undocumented* steps to perform, ie copying some libs in maven\lib directory. I can give you the complete listing in like two hours once I am at my job. On 3/29/06, Jens Riboe [EMAIL PROTECTED] wrote: I have succeed with FTP upload (deploy), but was surprised to find out that FTP download (repo/depends) failed. [WARNING] repository metadata for: 'artifact org.apache.maven.wagon:wagon-ftp' could not be retrieved from repository: myFTPsite due to an error: Unsupported Protocol: 'ftp': Cannot find wagon which supports the requested protocol: ftp Am I missing something? Or, is ftp m2 repo not supported? If not, will it be supported soon? Thanks for your help. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Alexandre Poitras Québec, Canada - 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]
[M2] mvn site:deploy throws an exception
I'm trying to use FTP for site deployment, but get an exception. Is FTP supported, for site upload? C:\temp\nnnmvn -e site:deploy + Error stacktraces are turned on. [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'site'. [INFO] [INFO] Building Whatever [INFO]task-segment: [site:deploy] [INFO] [INFO] [site:deploy] [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Wagon protocol 'ftp' doesn't support directory copying [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Wagon protocol 'ftp' doesn't support directory copying at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default LifecycleExecutor.java:559) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoa l(DefaultLifecycleExecutor.java:488) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultL ifecycleExecutor.java:458) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle Failures(DefaultLifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments( DefaultLifecycleExecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec ycleExecutor.java:140) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.MojoExecutionException: Wagon protocol 'ftp' doesn't support directory copying at org.apache.maven.plugins.site.SiteDeployMojo.execute(SiteDeployMojo.java :120) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMa nager.java:412) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default LifecycleExecutor.java:534) ... 16 more [INFO] [INFO] Total time: 2 seconds [INFO] Finished at: Wed Mar 29 23:12:06 CEST 2006 [INFO] Final Memory: 2M/6M [INFO] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[M2] Stacktrace when downloading from repo - HELP
Hi,
I got the following stack trace when trying to download from an internal
mvn2 repo.
from the specified remote repositories:
R (https://my.internal.host/mvn),
central (http://repo1.maven.org/maven2)
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(Defau
ltArtifactResolver.java:140)
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(Defau
ltArtifactResolver.java:63)
at
org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromReposit
ory(DefaultMavenProjectBuilder.java:386)
... 26 more
Caused by: org.apache.maven.wagon.TransferFailedException: Error
transferring file
at
org.apache.maven.wagon.providers.http.LightweightHttpWagon.fillInputData
(LightweightHttpWagon.java:99)
at org.apache.maven.wagon.StreamWagon.get(StreamWagon.java:68)
at
org.apache.maven.artifact.manager.DefaultWagonManager.getRemoteFile(Defa
ultWagonManager.java:369)
at
org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(Defaul
tWagonManager.java:282)
at
org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(Defaul
tWagonManager.java:244)
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(Defau
ltArtifactResolver.java:124)
... 28 more
Caused by: javax.net.ssl.SSLHandshakeException:
sun.security.validator.ValidatorException: PKIX path building failed:
sun.security.provider.certpath.SunCertPathBuilderException: unable to
find valid certification path to requested target
at
com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:150)
at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1476
)
at
com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:174)
at
com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:168)
at
com.sun.net.ssl.internal.ssl.ClientHandshaker.serverCertificate(ClientHa
ndshaker.java:847)
at
com.sun.net.ssl.internal.ssl.ClientHandshaker.processMessage(ClientHands
haker.java:106)
at
com.sun.net.ssl.internal.ssl.Handshaker.processLoop(Handshaker.java:495)
at
com.sun.net.ssl.internal.ssl.Handshaker.process_record(Handshaker.java:4
33)
at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java
:815)
at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSo
cketImpl.java:1025)
at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.
java:1038)
at
sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:402
)
at
sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(Ab
stractDelegateHttpsURLConnection.java:170)
at
sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnec
tion.java:913)
at
sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsUR
LConnectionImpl.java:234)
at
org.apache.maven.wagon.providers.http.LightweightHttpWagon.fillInputData
(LightweightHttpWagon.java:85)
... 33 more
Caused by: sun.security.validator.ValidatorException: PKIX path building
failed: sun.security.provider.certpath.SunCertPathBuilderException:
unable to find valid certification path to requested target
at
sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:221)
at
sun.security.validator.PKIXValidator.engineValidate(PKIXValidator.java:1
45)
at sun.security.validator.Validator.validate(Validator.java:203)
at
com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.checkServerTrusted(X50
9TrustManagerImpl.java:172)
at
com.sun.net.ssl.internal.ssl.JsseX509TrustManager.checkServerTrusted(SSL
ContextImpl.java:320)
at
com.sun.net.ssl.internal.ssl.ClientHandshaker.serverCertificate(ClientHa
ndshaker.java:840)
... 44 more
Caused by: sun.security.provider.certpath.SunCertPathBuilderException:
unable to find valid certification path to requested target
at
sun.security.provider.certpath.SunCertPathBuilder.engineBuild(SunCertPat
hBuilder.java:236)
at
java.security.cert.CertPathBuilder.build(CertPathBuilder.java:194)
at
sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:216)
... 49 more
Here is the pom.xml
project
. . .
nameFooBar/name
groupId foobar/groupId
artifactId${pom.name}/artifactId
version1.0/version
packagingjar/packaging
repositories
repository
idR/id
layoutdefault/layout
urlhttps://my.internal.host/mvn/url
/repository
/repositories
dependencies
dependency
groupIdsomeGroup/groupId
artifactIdsomeArtifact/artifactId
version1.0/version
scopecompile/scope
/dependency
/dependencies
/project
And here is the settings.xml
settings
servers
server
idR/id
[M2] repo access via https and clientCert
How do I configure Maven to download dependencies from a repository only accessible via HTTPS with client certificates? Thanks in advance, /Jens - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[M2] Can mvn access a repo via https + client cert?
Hi, Is it possible for maven to download files from a maven repo that can only be accessed via HTTPS with client certificates? The privateKey tag in the settings file, seems to only refer to ssh related uploads. Thanks in advance, /Jens - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Cannot run site:deploy using scpexe, but can run deploy:deploy using scpexe
Hi,
I have problem with site:deploy using scpexe. I'm running on WinXP with
putty installed.
scpexe://myHost/home/myUser/tools/MyTool - Session: Opened
Executing command: ssh -i C:\Documents and Settings\myUser\My
Documents\My Certificates\myHost.priv.ppk -o BatchMode yes
[EMAIL PROTECTED] mkdir -p /home/myUser/tools/MyTool/.
'ssh' is not recognized as an internal or external command, operable
program or batch file.
scpexe://myHost/home/myUser/tools/MyTool - Session: Disconnecting
In the source code of wagon sshext, I can see the check for putty
boolean putty = sshExecutable.indexOf( plink ) = 0;
There is several putty checks like
if ( putty )
{
cl.createArgument().setValue( -batch );
}
else
{
cl.createArgument().setValue( -o );
cl.createArgument().setValue( BatchMode yes );
}
So, based on this and the generated command line above I can conclude
that it does not pick up the settings.
However, I can successfully perform a deploy:deploy, which means the
settings are picked up by the deploy plugin, but not the site plugin.
Here is part of the settings file
servers
server
idmyServer/id
usernamemyUser/username
privateKeyC:\Documents and Settings\myUser\My Documents\My
Certificates\myHost.priv.ppk/privateKey
configuration
sshExecutableplink/sshExecutable
scpExecutablepscp/scpExecutable
sshArgs-v/sshArgs
/configuration
/server
/servers
Here is part of the pom
distributionManagement
repository
idmyServer/id
urlscpexe://myHost/home/myUser/M2/url
/repository
site
idmyServer/id
urlscpexe://myHost/home/myUser/tools/MyTool/url
/site
/distributionManagement
build
extensions
extension
groupIdorg.apache.maven.wagon/groupId
artifactIdwagon-ssh-external/artifactId
version1.0-alpha-6/version
/extension
/extensions
Any light on this 'show stopper' is highly appreciated.
/Jens
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[M 2.0.2] Cannot run site:deploy using scpexe, However can run deploy:deploy using scpexe
Hi,
I have problem running site:deploy using scpexe. It seems to me that it
does not pick up the settings (~\.m2\settings.xml), where plink/pscp are
defined.
However, this seems to work without problems when I run deploy:deploy to
the same host with the same settings as above (just another target
directory).
I'm using Maven 2.0.2 running on WinXP with putty installed.
Here are more details:
--- CMD ---
scpexe://myHost/home/myUser/tools/MyTool - Session: Opened Executing
command: ssh -i C:\Documents and Settings\myUser\My Documents\My
Certificates\myHost.priv.ppk -o BatchMode yes [EMAIL PROTECTED] mkdir -p
/home/myUser/tools/MyTool/.
'ssh' is not recognized as an internal or external command, operable
program or batch file.
scpexe://myHost/home/myUser/tools/MyTool - Session: Disconnecting
---END---
In the source code of wagon sshext, I can see the check for putty
boolean putty = sshExecutable.indexOf( plink ) = 0;
There is several putty checks like
if ( putty ) {
cl.createArgument().setValue( -batch );
} else {
cl.createArgument().setValue( -o );
cl.createArgument().setValue( BatchMode yes );
}
So, based on this and the generated command line above I can conclude
that it does not pick up the settings.
However, I can successfully perform a deploy:deploy, which means the
settings are picked up by the deploy plugin, but not the site plugin.
Here is a snippet from the settings file
servers
server
idmyServer/id
usernamemyUser/username
privateKeyC:\Documents and Settings\myUser\My Documents\My
Certificates\myHost.priv.ppk/privateKey
configuration
sshExecutableplink/sshExecutable
scpExecutablepscp/scpExecutable
sshArgs-v/sshArgs
/configuration
/server
/servers
Here is a snippet from the pom file
. . .
distributionManagement
repository
idmyServer/id
urlscpexe://myHost/home/myUser/M2/url
/repository
site
idmyServer/id
urlscpexe://myHost/home/myUser/tools/MyTool/url
/site
/distributionManagement
. . .
build
extensions
extension
groupIdorg.apache.maven.wagon/groupId
artifactIdwagon-ssh-external/artifactId
version1.0-alpha-6/version
/extension
/extensions
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-site-plugin/artifactId
configuration
localesen/locales
/configuration
/plugin
. . .
Any light on this 'show stopper' is highly appreciated.
/Jens
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Copying dependencies
You can use this Ant task http://www.ribomation.com/riboutils/DependencyList/ Cheers /jens Jesper Linvald wrote: Hello all, I need to copy all dependencies specified in my pom to a special directory before deployment - I cant use the ear task since I need a custom directory layout. Is there a way to do this with a plugin or do I need to script it? Regards Jesper Linvald - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Exectable RMI client and server jar
If you want to launch a RMI servant, as a stand-alone, from a JAR file you must change your program according to the following steps a) skip rmiregistry and create an internal registry thread instead http://java.sun.com/j2se/1.4.2/docs/api/java/rmi/registry/LocateRegistry.htm l#createRegistry(int) and bind your RMI servant to your internal registry http://java.sun.com/j2se/1.4.2/docs/api/java/rmi/registry/Registry.html#bind (java.lang.String,%20java.rmi.Remote) b) skip the policy file and register a permissive security manager instead http://java.sun.com/j2se/1.4.2/docs/api/java/rmi/RMISecurityManager.html subclass RMISecurityManager and implement an empty checkXyz() for each thrown SecurityException c) if you need dynamic client code loading, launch an internal (simple/tiny/limited) http server, which points to a directory of your class files, which should be available for your RMI client http://java.sun.com/j2se/1.4.2/docs/guide/rmi/spec/rmi-arch5.html d) declare the Main-Class JAR manifest attribute e) jar it together using Ant, before messing around with maven f) launch it using double-click or java -jar ... Kind regards, Jens Riboe -Original Message- From: news [mailto:[EMAIL PROTECTED] Behalf Of Geoffrey Sent: Monday, April 12, 2004 5:59 PM To: [EMAIL PROTECTED] Subject: Exectable RMI client and server jar Hi all, To run my RMI server I currently have to do this (straight from Sun's RMI tutorial): start %JAVA_HOME%\bin\rmiregistry java -Djava.rmi.server.codebase=file:/. -Djava.rmi.server.hostname=localhost -Djava.security.policy=java.policy mypackage.ServerEngine Is it possible to make a single executable jar configured in a way so the user only has to open it (java -jar or even a double click in windows)? - How do I configure Maven to configure the -D parameters in the generated jar? - Can I place my java.policy file in my jar? (so configure it as a resource in maven) - Can I make it call start rmiregistry? This one isn't so important as the rest, as this problem only occurs on the server and the others also occur on the client. Thanks for any and all help, Geoffrey - 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]
