Hi again
I am using the expresson language support like ${pom.artifactId} that
is official called ${project.artifactId} as I have understood.
And this does not solve the issue I am adressing here..
The issue is that the TRUNK or VV-SNAPSHOT version is located at url
... common/my-project/trunk
The tagged version in example 3.0 will be located at
... common/my-project/tags/my-project-3.0
The value "trunk" when snapshot and the value "tags/my-project-30" when
And I am searching for a way to express this without having to change
the pom.xml too much.
Therefore I am looking for expression variables that leverage out /
manage the CMS urls for the same artifact in different release stage.
Therefore I am looking for variables like:
${project.basePath} and ${project. versionPath}
with the functionality described in earlier mail below.
Maybe the problem is at a pom level. Maven seems not to deal with
trunk/tags/branches in its model ?
It is usage that deals with that. I mean how people setup and uses it..
In documentation for subversion it is a recommented usage to make the
"directory" tree like
my-project/trunk
my-project/tags
my-project/branches
But this is not reflected in maven (as I see it) Okay the maven
release plugin knows these rules, but it is programmed into the plugin.
/Anders
On 08/12/2008, at 08.13, Baptiste MATHUS wrote:
Hi Anders,
There's already variables that I guess you could use for your use
case.
Did you try putting something like this? :
<url>
http://my-site.xxx/sites/common/${pom.groupId}/${pom.artifactId}/$
{pom.version}<http://my-site.xxx/sites/common/my-project/tags/my-project-3.0
>
</url>
I'm not sure I got all your point from your message. If so, please
let us
know.
Cheers.
2008/12/8 Anders Kristian Andersen
<[EMAIL PROTECTED]>
Hi
I am working with at wish to make a site per release of my artifact
assume the following
The trunk: for "my-project"
<url>http://my-site.xxx/sites/common/my-project</url>
This means that the URL http://my-site.xxx/sites/common/my-project/contains
the site.
When I release the 3.0 version of my-project I want a released site
<url>http://my-site.xxx/sites/common/my-project/tags/my-
project-3.0</url>
The problem is that I manually have to change the URL in the released
artifacts to solve this.
I would like a property that makes this URL a constant in my pom.xml
An idea could be two properties property
1) project.basePath=**/common/my-project
** This property must probably be set in the pom, or guessed by
maven
when not set
2) project.versionPath="." when pom.xml is in a "trunk" directory
or
project.versionPath="tags/my-project-3.0" when the directory after
basePath is "tags", "branches" and directory after..
** This property should be calculated by maven based on the
standard
"usages" of directories trunk, tags, branches
Finally I want to be able to set the url to a value like
<url>http://my-site.xxx/sites/${project.basePath}/${project<http://my-site.xxx/sites/$%7Bproject.basePath%7D/$%7Bproject
>.
versionPath}</url>
My Questions are:
a) Is this possible already today? Am I just missing some Maven
knowledge?
b) Can I add property handlers to a project? I belive that a plugin
would
not be enough here ?
/Anders
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Baptiste <Batmat> MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
