Re: Parent POM, properties and scm problem
Might I suggest for the time being, to download and install the
maven-pom-plugin (
http://svn.apache.org/repos/asf/maven/sandbox/trunk/plugins/maven-pom-plugin/)
and manually manage the scm fields in the projects. I know it's a hack, but
non-standard layouts tend to produce non-standard solutions. Welcome to
convention over configuration :)
--
Eric Redmond
http://blog.propellors.net
On 8/6/07, Jörg Schaible [EMAIL PROTECTED] wrote:
Oscar Picasso wrote on Wednesday, August 01, 2007 7:31 PM:
The current Maven behaviour is fine for multimodule projects.
However I am trying to write a organizational POM that all my projets
would inherited and wanted to avoid duplication of the scm section.
So in case of independent projects it does not make sense to put all
them inside the same trunk.
I guess currently I cannot avoid this duplication.
Not really, and there's a simple reason: You cannot assume that everyone
keeps his organizational POM in the root of all the projects. Our
organizational POM has SCM URL entries that are used to release the
organizational POM itself. It does not even make sense to inherit them.
However, you may use properties to define the SCM URLs as we do:
scm
connectionscm|svn|${my.svn.root}${my.svn.tagBase}/trunk/connection
developerConnectionscm|svn|${my.svn.root}${my.svn.tagBase
}/trunk/developerConnection
url${my.svn.view}${my.svn.tagBase}/trunk/url
/scm
while my.svn.root and my.svn.view are properties that are defined in
the organizational POM and my.svn.tagBase is defined in the POM of the
project root (in case of a multi-module project). But keep in mind, that the
release-plugin will rewrite the URLs after the first release, so there are
no properties in the URL anymore anyway. So the whole definition is only
useful as template for new POMs.
- Jörg
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Parent POM, properties and scm problem
I'm also experiencing this problem. As discussed here (under Inheritance v.
Aggregation):
http://www.propellors.net/maven/site/pom.html#POM%20Relationships
it appears to make sense in what is called the aggregation use case, but
not in the inheritance use case. I'm wondering if there's some way to
simply disable this functionality (maybe setting a property? don't know...)
to get these url elements to inherit as one would expect - as is.
If this functionality isn't currently available, and somebody could point me
to the appropriate code, I would be happy to try and write a patch for it...
Thanks,
Jared
Oscar Picasso
Thu, 02 Aug 2007 06:31:58 -0700
That's exactly what I am doing.
And it works fine except for the problem that I mention in this thread of
the project artifactId being added to some urls like the scmConnection.
On 8/1/07, Bryan Loofbourrow [EMAIL PROTECTED] wrote:
I'm wondering if the following would work:
- Make your organizational pom project. Don't define any module entries
in
it.
- Have all of your projects depend on it as a parent
- Build and install your organizational pom to a central repository
accessible to all of your projects.
I'm thinking that you can then independently build and deploy your
organizational pom by itself, and have your projects use it, from the
repository, as a parent for definition purposes, though not build
purposes.
I'd be interested to know whether this works. It seems useful.
-- Bryan
-Original Message-
From: Oscar Picasso [EMAIL PROTECTED]
Sent: Wednesday, August 01, 2007 10:31 AM
To: Maven Users List
Subject: Re: Parent POM, properties and scm problem
The current Maven behaviour is fine for multimodule projects.
However I am trying to write a organizational POM that all my projets
would
inherited and wanted to avoid duplication of the scm section.
So in case of independent projects it does not make sense to put all them
inside the same trunk.
I guess currently I cannot avoid this duplication.
On 7/31/07, Eric Redmond [EMAIL PROTECTED] wrote:
Maven does this so that child module's scm can be defined once in the
parent.
scm
connectionscm:svn:https://url/project/trunk
/scm
modules
moduleChild
Then the Child module's scm url is automatically set as:
scm
connectionscm:svn:https://url/project/trunk/Child
/scm
Which is the convention for a multi-module project.
If your Child project has to be seperate, with it's own trunk, etc. I
would suggest (if svn) using svn:externals to access the child under the
parent project. Since it ownly appends the name on a multi-module
project,
I'm trying to figure out how you locally check out your project...
perhaps
create a trunks-style setup in your version control would be best?
Eric
On 7/30/07, Oscar Picasso [EMAIL PROTECTED] wrote:
I have also noticed the same behavior with the project url, the sit
url
and
the scm url even if in the effective the corresponding properties are
correct (without the artifactId appended).
On 7/30/07, Oscar Picasso [EMAIL PROTECTED] wrote:
Hi,
In the parent POM I have the following:
[...]
properties
scmConnection
http://localhost/repos/repo/${groupId}/${artifactId}/trunk
http://localhost/repos/repo/$%7BgroupId%7D/$%7BartifactId%7D/trunk
http://localhost/repos/repo/$%7BgroupId%7D/$%7BartifactId%7D/trunk
/scmConnection
/properties
scm
connection${scmConnection}/connection
developerConnection${scmConnection}/developerConnection
/scm
[...]
The child POM has nothing expect mandatory elements and the
reference
to
the parent POM. Both the child and the parent are snapshots. The
parent
POM
has been deployed to the remote repository.
When I run mvn help:effective-pom on the child project, I get:
[...]
scm
connection
http://localhost/repos/repo/com.opicasso/Child/trunk/Child
/connection
developerConnection
http://localhost/repos/repo/com.opicasso/Child/trunk/Child
/developerConnection
/scm
[..]
I would have expected:
[...]
scm
connectionhttp://localhost/repos/repo/com.opicasso/Child/trunk
/connection
developerConnection
http://localhost/repos/repo/com.opicasso/Child/trunk
/developerConnection
/scm
[..]
Why does maven happen the child artifactId to the connections? Does
maven
merge the parent scm connections with the children ones ? But in the
current
case the child has no scm connections defined in its pom.
How to get rid of this extra artifactId?
Thanks
Oscar
--
Eric Redmond
http://blog.propellors.net
RE: Parent POM, properties and scm problem
Oscar Picasso wrote on Wednesday, August 01, 2007 7:31 PM:
The current Maven behaviour is fine for multimodule projects.
However I am trying to write a organizational POM that all my projets
would inherited and wanted to avoid duplication of the scm section.
So in case of independent projects it does not make sense to put all
them inside the same trunk.
I guess currently I cannot avoid this duplication.
Not really, and there's a simple reason: You cannot assume that everyone keeps
his organizational POM in the root of all the projects. Our organizational
POM has SCM URL entries that are used to release the organizational POM
itself. It does not even make sense to inherit them.
However, you may use properties to define the SCM URLs as we do:
scm
connectionscm|svn|${my.svn.root}${my.svn.tagBase}/trunk/connection
developerConnectionscm|svn|${my.svn.root}${my.svn.tagBase}/trunk/developerConnection
url${my.svn.view}${my.svn.tagBase}/trunk/url
/scm
while my.svn.root and my.svn.view are properties that are defined in the
organizational POM and my.svn.tagBase is defined in the POM of the project
root (in case of a multi-module project). But keep in mind, that the
release-plugin will rewrite the URLs after the first release, so there are no
properties in the URL anymore anyway. So the whole definition is only useful as
template for new POMs.
- Jörg
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Parent POM, properties and scm problem
That's exactly what I am doing.
And it works fine except for the problem that I mention in this thread of
the project artifactId being added to some urls like the scmConnection.
On 8/1/07, Bryan Loofbourrow [EMAIL PROTECTED] wrote:
I'm wondering if the following would work:
- Make your organizational pom project. Don't define any module entries
in
it.
- Have all of your projects depend on it as a parent
- Build and install your organizational pom to a central repository
accessible to all of your projects.
I'm thinking that you can then independently build and deploy your
organizational pom by itself, and have your projects use it, from the
repository, as a parent for definition purposes, though not build
purposes.
I'd be interested to know whether this works. It seems useful.
-- Bryan
-Original Message-
From: Oscar Picasso [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 01, 2007 10:31 AM
To: Maven Users List
Subject: Re: Parent POM, properties and scm problem
The current Maven behaviour is fine for multimodule projects.
However I am trying to write a organizational POM that all my projets
would
inherited and wanted to avoid duplication of the scm section.
So in case of independent projects it does not make sense to put all them
inside the same trunk.
I guess currently I cannot avoid this duplication.
On 7/31/07, Eric Redmond [EMAIL PROTECTED] wrote:
Maven does this so that child module's scm can be defined once in the
parent.
scm
connectionscm:svn:https://url/project/trunk
/scm
modules
moduleChild
Then the Child module's scm url is automatically set as:
scm
connectionscm:svn:https://url/project/trunk/Child
/scm
Which is the convention for a multi-module project.
If your Child project has to be seperate, with it's own trunk, etc. I
would suggest (if svn) using svn:externals to access the child under the
parent project. Since it ownly appends the name on a multi-module
project,
I'm trying to figure out how you locally check out your project...
perhaps
create a trunks-style setup in your version control would be best?
Eric
On 7/30/07, Oscar Picasso [EMAIL PROTECTED] wrote:
I have also noticed the same behavior with the project url, the sit
url
and
the scm url even if in the effective the corresponding properties are
correct (without the artifactId appended).
On 7/30/07, Oscar Picasso [EMAIL PROTECTED] wrote:
Hi,
In the parent POM I have the following:
[...]
properties
scmConnection
http://localhost/repos/repo/${groupId}/${artifactId}/trunk
http://localhost/repos/repo/$%7BgroupId%7D/$%7BartifactId%7D/trunk
/scmConnection
/properties
scm
connection${scmConnection}/connection
developerConnection${scmConnection}/developerConnection
/scm
[...]
The child POM has nothing expect mandatory elements and the
reference
to
the parent POM. Both the child and the parent are snapshots. The
parent
POM
has been deployed to the remote repository.
When I run mvn help:effective-pom on the child project, I get:
[...]
scm
connection
http://localhost/repos/repo/com.opicasso/Child/trunk/Child
/connection
developerConnection
http://localhost/repos/repo/com.opicasso/Child/trunk/Child
/developerConnection
/scm
[..]
I would have expected:
[...]
scm
connectionhttp://localhost/repos/repo/com.opicasso/Child/trunk
/connection
developerConnection
http://localhost/repos/repo/com.opicasso/Child/trunk
/developerConnection
/scm
[..]
Why does maven happen the child artifactId to the connections? Does
maven
merge the parent scm connections with the children ones ? But in the
current
case the child has no scm connections defined in its pom.
How to get rid of this extra artifactId?
Thanks
Oscar
--
Eric Redmond
http://blog.propellors.net
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Parent POM, properties and scm problem
The current Maven behaviour is fine for multimodule projects.
However I am trying to write a organizational POM that all my projets would
inherited and wanted to avoid duplication of the scm section.
So in case of independent projects it does not make sense to put all them
inside the same trunk.
I guess currently I cannot avoid this duplication.
On 7/31/07, Eric Redmond [EMAIL PROTECTED] wrote:
Maven does this so that child module's scm can be defined once in the
parent.
scm
connectionscm:svn:https://url/project/trunk
/scm
modules
moduleChild
Then the Child module's scm url is automatically set as:
scm
connectionscm:svn:https://url/project/trunk/Child
/scm
Which is the convention for a multi-module project.
If your Child project has to be seperate, with it's own trunk, etc. I
would suggest (if svn) using svn:externals to access the child under the
parent project. Since it ownly appends the name on a multi-module project,
I'm trying to figure out how you locally check out your project... perhaps
create a trunks-style setup in your version control would be best?
Eric
On 7/30/07, Oscar Picasso [EMAIL PROTECTED] wrote:
I have also noticed the same behavior with the project url, the sit url
and
the scm url even if in the effective the corresponding properties are
correct (without the artifactId appended).
On 7/30/07, Oscar Picasso [EMAIL PROTECTED] wrote:
Hi,
In the parent POM I have the following:
[...]
properties
scmConnection
http://localhost/repos/repo/${groupId}/${artifactId}/trunk
http://localhost/repos/repo/$%7BgroupId%7D/$%7BartifactId%7D/trunk
/scmConnection
/properties
scm
connection${scmConnection}/connection
developerConnection${scmConnection}/developerConnection
/scm
[...]
The child POM has nothing expect mandatory elements and the reference
to
the parent POM. Both the child and the parent are snapshots. The
parent
POM
has been deployed to the remote repository.
When I run mvn help:effective-pom on the child project, I get:
[...]
scm
connection
http://localhost/repos/repo/com.opicasso/Child/trunk/Child
/connection
developerConnection
http://localhost/repos/repo/com.opicasso/Child/trunk/Child
/developerConnection
/scm
[..]
I would have expected:
[...]
scm
connectionhttp://localhost/repos/repo/com.opicasso/Child/trunk
/connection
developerConnection
http://localhost/repos/repo/com.opicasso/Child/trunk
/developerConnection
/scm
[..]
Why does maven happen the child artifactId to the connections? Does
maven
merge the parent scm connections with the children ones ? But in the
current
case the child has no scm connections defined in its pom.
How to get rid of this extra artifactId?
Thanks
Oscar
--
Eric Redmond
http://blog.propellors.net
RE: Parent POM, properties and scm problem
I'm wondering if the following would work:
- Make your organizational pom project. Don't define any module entries in
it.
- Have all of your projects depend on it as a parent
- Build and install your organizational pom to a central repository
accessible to all of your projects.
I'm thinking that you can then independently build and deploy your
organizational pom by itself, and have your projects use it, from the
repository, as a parent for definition purposes, though not build purposes.
I'd be interested to know whether this works. It seems useful.
-- Bryan
-Original Message-
From: Oscar Picasso [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 01, 2007 10:31 AM
To: Maven Users List
Subject: Re: Parent POM, properties and scm problem
The current Maven behaviour is fine for multimodule projects.
However I am trying to write a organizational POM that all my projets would
inherited and wanted to avoid duplication of the scm section.
So in case of independent projects it does not make sense to put all them
inside the same trunk.
I guess currently I cannot avoid this duplication.
On 7/31/07, Eric Redmond [EMAIL PROTECTED] wrote:
Maven does this so that child module's scm can be defined once in the
parent.
scm
connectionscm:svn:https://url/project/trunk
/scm
modules
moduleChild
Then the Child module's scm url is automatically set as:
scm
connectionscm:svn:https://url/project/trunk/Child
/scm
Which is the convention for a multi-module project.
If your Child project has to be seperate, with it's own trunk, etc. I
would suggest (if svn) using svn:externals to access the child under the
parent project. Since it ownly appends the name on a multi-module project,
I'm trying to figure out how you locally check out your project... perhaps
create a trunks-style setup in your version control would be best?
Eric
On 7/30/07, Oscar Picasso [EMAIL PROTECTED] wrote:
I have also noticed the same behavior with the project url, the sit url
and
the scm url even if in the effective the corresponding properties are
correct (without the artifactId appended).
On 7/30/07, Oscar Picasso [EMAIL PROTECTED] wrote:
Hi,
In the parent POM I have the following:
[...]
properties
scmConnection
http://localhost/repos/repo/${groupId}/${artifactId}/trunk
http://localhost/repos/repo/$%7BgroupId%7D/$%7BartifactId%7D/trunk
/scmConnection
/properties
scm
connection${scmConnection}/connection
developerConnection${scmConnection}/developerConnection
/scm
[...]
The child POM has nothing expect mandatory elements and the reference
to
the parent POM. Both the child and the parent are snapshots. The
parent
POM
has been deployed to the remote repository.
When I run mvn help:effective-pom on the child project, I get:
[...]
scm
connection
http://localhost/repos/repo/com.opicasso/Child/trunk/Child
/connection
developerConnection
http://localhost/repos/repo/com.opicasso/Child/trunk/Child
/developerConnection
/scm
[..]
I would have expected:
[...]
scm
connectionhttp://localhost/repos/repo/com.opicasso/Child/trunk
/connection
developerConnection
http://localhost/repos/repo/com.opicasso/Child/trunk
/developerConnection
/scm
[..]
Why does maven happen the child artifactId to the connections? Does
maven
merge the parent scm connections with the children ones ? But in the
current
case the child has no scm connections defined in its pom.
How to get rid of this extra artifactId?
Thanks
Oscar
--
Eric Redmond
http://blog.propellors.net
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Parent POM, properties and scm problem
Maven does this so that child module's scm can be defined once in the
parent.
scm
connectionscm:svn:https://url/project/trunk
/scm
modules
moduleChild
Then the Child module's scm url is automatically set as:
scm
connectionscm:svn:https://url/project/trunk/Child
/scm
Which is the convention for a multi-module project.
If your Child project has to be seperate, with it's own trunk, etc. I
would suggest (if svn) using svn:externals to access the child under the
parent project. Since it ownly appends the name on a multi-module project,
I'm trying to figure out how you locally check out your project... perhaps
create a trunks-style setup in your version control would be best?
Eric
On 7/30/07, Oscar Picasso [EMAIL PROTECTED] wrote:
I have also noticed the same behavior with the project url, the sit url
and
the scm url even if in the effective the corresponding properties are
correct (without the artifactId appended).
On 7/30/07, Oscar Picasso [EMAIL PROTECTED] wrote:
Hi,
In the parent POM I have the following:
[...]
properties
scmConnection
http://localhost/repos/repo/${groupId}/${artifactId}/trunk
http://localhost/repos/repo/$%7BgroupId%7D/$%7BartifactId%7D/trunk
/scmConnection
/properties
scm
connection${scmConnection}/connection
developerConnection${scmConnection}/developerConnection
/scm
[...]
The child POM has nothing expect mandatory elements and the reference to
the parent POM. Both the child and the parent are snapshots. The parent
POM
has been deployed to the remote repository.
When I run mvn help:effective-pom on the child project, I get:
[...]
scm
connection
http://localhost/repos/repo/com.opicasso/Child/trunk/Child
/connection
developerConnection
http://localhost/repos/repo/com.opicasso/Child/trunk/Child
/developerConnection
/scm
[..]
I would have expected:
[...]
scm
connectionhttp://localhost/repos/repo/com.opicasso/Child/trunk
/connection
developerConnection
http://localhost/repos/repo/com.opicasso/Child/trunk
/developerConnection
/scm
[..]
Why does maven happen the child artifactId to the connections? Does
maven
merge the parent scm connections with the children ones ? But in the
current
case the child has no scm connections defined in its pom.
How to get rid of this extra artifactId?
Thanks
Oscar
--
Eric Redmond
http://blog.propellors.net
Parent POM, properties and scm problem
Hi,
In the parent POM I have the following:
[...]
properties
scmConnection
http://localhost/repos/repo/${groupId}/${artifactId}/trunk/scmConnection
/properties
scm
connection${scmConnection}/connection
developerConnection${scmConnection}/developerConnection
/scm
[...]
The child POM has nothing expect mandatory elements and the reference to the
parent POM. Both the child and the parent are snapshots. The parent POM has
been deployed to the remote repository.
When I run mvn help:effective-pom on the child project, I get:
[...]
scm
connectionhttp://localhost/repos/repo/com.opicasso/Child/trunk/Child
/connection
developerConnection
http://localhost/repos/repo/com.opicasso/Child/trunk/Child
/developerConnection
/scm
[..]
I would have expected:
[...]
scm
connectionhttp://localhost/repos/repo/com.opicasso/Child/trunk
/connection
developerConnection
http://localhost/repos/repo/com.opicasso/Child/trunk/developerConnection
/scm
[..]
Why does maven happen the child artifactId to the connections? Does maven
merge the parent scm connections with the children ones ? But in the current
case the child has no scm connections defined in its pom.
How to get rid of this extra artifactId?
Thanks
Oscar
Re: Parent POM, properties and scm problem
I have also noticed the same behavior with the project url, the sit url and
the scm url even if in the effective the corresponding properties are
correct (without the artifactId appended).
On 7/30/07, Oscar Picasso [EMAIL PROTECTED] wrote:
Hi,
In the parent POM I have the following:
[...]
properties
scmConnectionhttp://localhost/repos/repo/${groupId}/${artifactId}/trunk
http://localhost/repos/repo/$%7BgroupId%7D/$%7BartifactId%7D/trunk
/scmConnection
/properties
scm
connection${scmConnection}/connection
developerConnection${scmConnection}/developerConnection
/scm
[...]
The child POM has nothing expect mandatory elements and the reference to
the parent POM. Both the child and the parent are snapshots. The parent POM
has been deployed to the remote repository.
When I run mvn help:effective-pom on the child project, I get:
[...]
scm
connectionhttp://localhost/repos/repo/com.opicasso/Child/trunk/Child
/connection
developerConnection
http://localhost/repos/repo/com.opicasso/Child/trunk/Child
/developerConnection
/scm
[..]
I would have expected:
[...]
scm
connectionhttp://localhost/repos/repo/com.opicasso/Child/trunk
/connection
developerConnection
http://localhost/repos/repo/com.opicasso/Child/trunk/developerConnection
/scm
[..]
Why does maven happen the child artifactId to the connections? Does maven
merge the parent scm connections with the children ones ? But in the current
case the child has no scm connections defined in its pom.
How to get rid of this extra artifactId?
Thanks
Oscar
Re: Re: SCM Problem Continuum 1.0.3 Ant
hi emmanuel, seems i jumped the gun a bit on that problem. the first time i copy/pasted the scm url from another project and edited it according to the projects needs. that didn't work. when i entered the url manually everything worked just fine. sorry for making such a fuzz about nothing. thx again, Freundliche Grüße / With kind regards Thomas Zirke SN AG Klingenderstr. 5 D 33100 Paderborn voice +49 5251/1581-984 fax +49 5251/1581-71 eMail [EMAIL PROTECTED] Web http://www.s-und-n.de Vorstand Klaus Beverungen Josef Tillmann Vorsitzender des Aufsichtsrates Heinz-Dieter Wendorff Handelsregister Amtsgericht Paderborn HRB 3270 [EMAIL PROTECTED] 09.05.2007 11:42 Bitte antworten an continuum-users An: [EMAIL PROTECTED] Kopie: Thema: Antwort: Re: SCM Problem Continuum 1.0.3 Ant hi emmanuel, i don't get past the setup page. whenever i try to submit the form right beneath the scm url input field the following error message appears. [ You must provide an scm url ] i just checked the wrapper log and the ant project is not to be found in it. Freundliche Grüße / With kind regards Thomas Zirke SN AG Klingenderstr. 5 D 33100 Paderborn voice +49 5251/1581-984 fax +49 5251/1581-71 eMail [EMAIL PROTECTED] Web http://www.s-und-n.de Vorstand Klaus Beverungen Josef Tillmann Vorsitzender des Aufsichtsrates Heinz-Dieter Wendorff Handelsregister Amtsgericht Paderborn HRB 3270 Emmanuel Venisse [EMAIL PROTECTED] 09.05.2007 11:34 Bitte antworten an continuum-users An: [EMAIL PROTECTED] Kopie: Thema: Re: SCM Problem Continuum 1.0.3 Ant [EMAIL PROTECTED] a écrit : hi, i'm trying to setup the first ant based project in continuum 1.0.3. however i can't get past the SCM URL that is to be entered on the projects setup page. i do use the following connection string: scm:cvs:ext:username@server:/path/to/repository i tried this with and without the username it doesn't work in either case. i also tried to add the module i want to check out to the scm url as the following pattern shows scm:cvs:ext:username@server:/path/to/repository:Module/ What is the pb with this url? it's seems to be correct. Do you have some logs we can look at? this doesn't work either. setting up the scm url as such works fine with any maven2 project on the continuum server. can anyone help me with this problem? thanks in advance, Freundliche Grüße / With kind regards Thomas Zirke
Scm problem
I've been on 1.0.2 for a while and so thought I'd move on up to one of the 1.1 rcs. I'm having trouble with rc3 though - when I do certain scm operations it fails. e.g. scm:update scm:update: [echo] Updating from SCM BUILD FAILED File.. file:/C:/Temp/.maven/cache/maven-scm-plugin-1.5/plugin.jelly Element... scm:update Line.. 131 Column 138 org.apache.maven.scm.manager.ScmManager.update(Lorg/apache/maven/scm/rep ository/ScmRepository;Lorg/apache/maven/scm/ScmFileSet;Ljava/lang/String ;)Lorg/apache/maven/scm/command/update/UpdateScmResult; This is the repo section from my project.xml: repository connectionscm:cvs:pserver:[EMAIL PROTECTED]:/home/eu_fid_source/eufidetradec vs:Jdialtone/connection developerConnectionscm:cvs:pserver:[EMAIL PROTECTED]:/home/eu_fid _source/eufidetradecvs:Jdialtone/developerConnection /repository Running scm:parse-connection shows it's working things out from the url fine, so I'm not sure what could be wrong. Using rc2 is absolutely fine though. Any ideas? I have had a browse through the archives but I can't see anything that looks like the answer thanks James -- This message is intended only for the personal and confidential use of the designated recipient(s) named above. If you are not the intended recipient of this message you are hereby notified that any review, dissemination, distribution or copying of this message is strictly prohibited. This communication is for information purposes only and should not be regarded as an offer to sell or as a solicitation of an offer to buy any financial product, an official confirmation of any transaction, or as an official statement of Lehman Brothers. Email transmission cannot be guaranteed to be secure or error-free. Therefore, we do not represent that this information is complete or accurate and it should not be relied upon as such. All information is subject to change without notice. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[scm] Problem Running scm:bootstrap-project
I'm trying to get the scm:bootstrap-project working and am running into a
problem.
I'm running 'maven scm:boostrap-project -Dmaven.scm.cvs.module=edog' from
c:\projects\crap\scm. The cvs checkout completes successfully (creating
c:\projects\crap\scm\edog) but when it tries to run my bootstrap goal I get
an error.
In my bootstrap goal I'm doing the following...
util:available file=${maven.conf.dir}/${pom.artifactId}.filters
ant:filter
filtersfile=${maven.conf.dir}/${pom.artifactId}.filters/
/util:available
And am getting an error...
file:/c:/tools/apache/maven_local/plugins/maven-mis-util-plugin-1.0.0/:86:84
: a
nt:filter Must specify a file not a directory in the filtersfile
attribute:C:\p
rojects\crap\scm\edog\edog\src\conf\edog.filters
com.werken.werkz.UnattainableGoalException: Unable to obtain goal
[scm:bootstrap
-project] --
file:/c:/tools/apache/maven_local/plugins/maven-scm-plugin-1.1/:77:
9: maven:maven
file:/c:/tools/apache/maven_local/plugins/maven-mis-util-plugin
-1.0.0/:86:84: ant:filter Must specify a file not a directory in the
filtersfi
le attribute:C:\projects\crap\scm\edog\edog\src\conf\edog.filters
Apparently, the file path is correct when the util:available is evaluated
or else we would never get inside the body of the tag. However, when the
ant:filter is evaluated an extra 'edog' is added into the absolute file
path.
Any ideas?
--Norm
--
Norm Deane
MIS Consultant
Vanderbilt University
(615) 322-7855
[EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: [scm] Problem Running scm:bootstrap-project
Dsoes maven.conf.dir include ${basedir}? It looks like an additional edog
path is being added.
- Brett
-Original Message-
From: Norm Deane [mailto:[EMAIL PROTECTED]
Sent: Wednesday, 28 January 2004 3:22 AM
To: Maven Users List
Subject: [scm] Problem Running scm:bootstrap-project
I'm trying to get the scm:bootstrap-project working and am
running into a problem.
I'm running 'maven scm:boostrap-project
-Dmaven.scm.cvs.module=edog' from c:\projects\crap\scm. The
cvs checkout completes successfully (creating
c:\projects\crap\scm\edog) but when it tries to run my
bootstrap goal I get an error.
In my bootstrap goal I'm doing the following...
util:available
file=${maven.conf.dir}/${pom.artifactId}.filters
ant:filter
filtersfile=${maven.conf.dir}/${pom.artifactId}.filters/
/util:available
And am getting an error...
file:/c:/tools/apache/maven_local/plugins/maven-mis-util-plugin-1.0.0/:86:84
: a
nt:filter Must specify a file not a directory in the filtersfile
attribute:C:\p rojects\crap\scm\edog\edog\src\conf\edog.filters
com.werken.werkz.UnattainableGoalException: Unable to obtain goal
[scm:bootstrap -project] --
file:/c:/tools/apache/maven_local/plugins/maven-scm-plugin-1.1/:77:
9: maven:maven
file:/c:/tools/apache/maven_local/plugins/maven-mis-util-plugin
-1.0.0/:86:84: ant:filter Must specify a file not a directory in the
filtersfi le attribute:C:\projects\crap\scm\edog\edog\src\conf\edog.filters
Apparently, the file path is correct when the util:available is evaluated
or else we would never get inside the body of the tag. However, when the
ant:filter is evaluated an extra 'edog' is added into the absolute file
path.
Any ideas?
--Norm
--
Norm Deane
MIS Consultant
Vanderbilt University
(615) 322-7855
[EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
