You really mean 2.2 or 2.1? The roadmap is here:
http://jira.codehaus.org/browse/MSITE?report=com.atlassian.jira.plugin.system.project:roadmap-panel
and 2.1 will include doxia 1.1.2. Timeline there is none.
You might also have a look at the related Doxia release plan:
Oops, sorry meant 2.1. Hope it coming soon
ltheussl wrote:
You really mean 2.2 or 2.1? The roadmap is here:
http://jira.codehaus.org/browse/MSITE?report=com.atlassian.jira.plugin.system.project:roadmap-panel
and 2.1 will include doxia 1.1.2. Timeline there is none.
You might also
Just stumbled over the relativePath element, which I assume will solve my
warning, a case of rtfm there...
On 12/05/06, Mikael Andersson [EMAIL PROTECTED] wrote:
Hi
When I try to run mvn site:site in a child module I get the following
warning message:
[WARNING] Unable to load parent project
Maybe with site:attach-descriptor.
On 2/28/06, Alexandre Poitras [EMAIL PROTECTED] wrote:
Hi,
I am using the lastest site plugin snapshot and it seems to work fine
except that it seems to not find my site.xml file. I can't find the
correct property to set. Anyone know what is the default
ok I was wrong the problem wasn't there.
On 2/28/06, Alexandre Poitras [EMAIL PROTECTED] wrote:
Maybe with site:attach-descriptor.
On 2/28/06, Alexandre Poitras [EMAIL PROTECTED] wrote:
Hi,
I am using the lastest site plugin snapshot and it seems to work fine
except that it seems to
See: http://jira.codehaus.org/browse/WAGON-30
Replacing the jar in your maven/lib directory as indicated in the
comments should work, it worked for me.
--tom
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands,
to Maven Users List
To: Maven Users List users@maven.apache.org
cc:
Subject:Re: [m2] Site Plugin Cannot Overrite Site Files when
using file:/// p
rotocol.
See: http://jira.codehaus.org/browse/WAGON-30
Replacing the jar in your maven/lib directory as indicated
Many thanks Tom.
Chris
-Original Message-
From: Tomislav Stojcevich [mailto:[EMAIL PROTECTED]
Sent: 06 February 2006 16:31
To: Maven Users List
Subject: Re: [m2] Site Plugin Cannot Overrite Site Files when using file:///
p rotocol.
See: http://jira.codehaus.org/browse/WAGON-30
Tomislav Stojcevich [EMAIL PROTECTED]
02/06/2006 10:30 AM
Please respond to Maven Users List
To: Maven Users List users@maven.apache.org
cc:
Subject:Re: [m2] Site Plugin Cannot Overrite Site Files
when using file:/// p
rotocol.
See: http://jira.codehaus.org
S orry about that I accident sent the message out early:
I have the following layout
src
|- site
|-xdoc
| |-folder1
| |-folder2
|-resources
|-images
|-logo.gif
In site.xml I have the dollowing XML fragment
bannerRight
Hi Mark,
You are right. Can you file it in JIRA?
Regards,
Vincent
-Original Message-
From: Mark Kuzmycz [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 05, 2005 8:09 AM
To: users@maven.apache.org
Subject: RE: [m2] site plugin
S orry about that I accident sent the message
:09 AM
To: users@maven.apache.org
Subject: RE: [m2] site plugin
S orry about that I accident sent the message out early:
I have the following layout
src
|- site
|-xdoc
| |-folder1
| |-folder2
|-resources
|-images
|-logo.gif
In site.xml I
I was unde the impression that this was an m1 feature. I haven't used
M1 extensively however so I'm perfectly ready to be proved wrong ;)
Regards
On 23/09/05, Brett Porter [EMAIL PROTECTED] wrote:
No, not yet. There is an open JIRA issue to watch/comment on.
Our first priority now is
No, not yet. There is an open JIRA issue to watch/comment on.
Our first priority now is matching the m1 feature set.
- Brett
On 9/23/05, Nelson Arape [EMAIL PROTECTED] wrote:
Hello fellows
In maven-beta1, Does site plugin support consolidated reports from
sub-projects in a multiproject
What goal did you specify? site:site? or site: deploy?
puschteblume wrote:
Hi
I have following entry in pom.xml:
project
build
sourceDirectorysrc/main/sourceDirectory
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-site-plugin/artifactId
Hi Heiko,
If I understand correctly, you run 'm2 site:site', and you wonder
why the output ends up in 'target/site' instead of in '${basedir}/www'.
shouldn't you specify the 'outputDirectory' property instead ??
Dennis
On 7/1/05, puschteblume [EMAIL PROTECTED] wrote:
Hi
I have
Anyway, if you're deploying the site you should use site:deploy.
Also, siteDirectory is where your site files are. The files in
siteDirectory are zipped into the workingDirectory.
So, if you want to deploy your site to ${basedir}/www, you should put
that to workingDirectory like so:
Hm, this makes sense :)
You are completely right. And I am completely stupid.
Thanks for your help.
Dennis Geurts wrote:
Hi Heiko,
If I understand correctly, you run 'm2 site:site', and you wonder
why the output ends up in 'target/site' instead of in '${basedir}/www'.
shouldn't you specify
Hi Edwin
Thanks for your explanation. I have solved the problem, but it is
interesting what you told I haven't thought about. It is of course
better to leave things where they are and deploy it to the right
location. But I have a project that is under source control, and if you
can't ssh/scp
19 matches
Mail list logo