The JIRA report should go into the doxia sub-site (and corresponding
doxia-sitetools, etc), then you link to that from the base site for each
sub-project. WDYT?
-Lukas
Hervé BOUTEMY wrote:
notice that I tried to commit improvements based on previous thoughts and
found in index.apt.vm the f
notice that I tried to commit improvements based on previous thoughts and
found in index.apt.vm the following link: {{{./jira-report.html}Release Notes
for ${doxiaVersion}}}
And since the Jira report isn't available in Doxia "base" site, if you simply
remove the actual JIRA report from Doxia si
The Doxia site expert is Vincent Siveton: I hope he can express his opinion
Doxia (base + sitetools + tools) deserves IMHO the dedicated menus from the
actual Doxia site [1] to let people understand: it can/should be improved, but
if we merge the Doxia site with regular Maven site, we loose this
+1
notice I just created MSKINS-40: not really critical, should not block this
release since the table issue is really too much, but annoying
Regards,
Hervé
Le mardi 27 mars 2012 10:01:16 Simone Tripodi a écrit :
> Hi all guys,
> I'm opening a thread vote today for releasing Apache Maven Fluid
You can create a mirror. If you supply the right id, it will simply work.
http://maven.apache.org/guides/mini/guide-mirror-settings.html
--
-- Aldrin Leal, / http://meadiciona.com/aldrinleal
On Tue, Mar 27, 2012 at 11:17 AM, ryenus blatt wrote:
> hello,
>
> in pom.xml, is it possible to setu
2012/3/27 Jason Dillon :
> Why don't you just fix the parsers in older mavens (ie. make a new release of
> old-maven-version-x w/fixed parser) that allows for changes in newer versions?
>
> Seems like if you can never add new information to the pom to solve
> problems/add features in Maven 3 w/o
Why don't you just fix the parsers in older mavens (ie. make a new release of
old-maven-version-x w/fixed parser) that allows for changes in newer versions?
Seems like if you can never add new information to the pom to solve
problems/add features in Maven 3 w/o completely breaking Maven 2, then
Hi Jesse!!
Breadcrumbs usually are defined inside the element in
site.xml: in the case of the fluido skin site, they are defined in the
skin parent site descriptor[1] that are merged with the ones of maven
parent and then inherited via . A little complex
chain.
Anyway, if you need to define brea
+1, such a small but crucial thing we missed last time. Looking much
better now.
thanks,
-Robert
Op Tue, 27 Mar 2012 12:39:19 +0200 schreef Tony Chemit
:
On Tue, 27 Mar 2012 10:01:16 +0200
Simone Tripodi wrote:
Hi all guys,
I'm opening a thread vote today for releasing Apache Maven Fl
Github user lweller closed the pull request at
https://github.com/apache/maven-release/pull/1
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Greetings,
On Tue, Mar 27, 2012 at 4:01 AM, Simone Tripodi
wrote:
> Staging repo:
> https://repository.apache.org/content/repositories/maven-118/
I'm using topbar and sidebar basic menus, but I'm not seeing any bread
crumbs being created in the little area underneath the left and right
nav areas
On Tue, 27 Mar 2012 10:01:16 +0200
Simone Tripodi wrote:
> Hi all guys,
> I'm opening a thread vote today for releasing Apache Maven Fluido Skin
> 1.2.1, based on RC1
oh yeah :)
+1 non binding
thanks,
tony.
>
> We solved 3 issues:
> https://jira.codehaus.org/secure/ReleaseNote.jspa?projectI
+1
2012/3/27 Simone Tripodi :
> Hi all guys,
> I'm opening a thread vote today for releasing Apache Maven Fluido Skin
> 1.2.1, based on RC1
>
> We solved 3 issues:
> https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11430&styleName=Html&version=18380
>
> where [MSKINS-38] is the major is
Hi all guys,
I'm opening a thread vote today for releasing Apache Maven Fluido Skin
1.2.1, based on RC1
We solved 3 issues:
https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11430&styleName=Html&version=18380
where [MSKINS-38] is the major issue that drove the new RC
There are three ne
14 matches
Mail list logo
