If you write documentation in Maven core (the components), not in Maven site
(the global project), you'll be happy with git like you do with sources
I can then take care of svnpubsub publication, or anybody else since I already
prepared it
(notice ranting against svnpubsub is just a waste of tim
I'm on vacation, with weak mobile connexion...
I'll try m-dependency-tree when back home
Id You updates m-dependency-p to latest -tree, the hope was it would work
without more efforts
Envoyé depuis mon mobile
- Reply message -
De : "Jason van Zyl"
Pour : "Maven Developers List"
Objet :
For Maven, wé nées it since java packages are shared between modules
For scm, where java packages are dedicated to modules, tes aggregated doc is
sufficient
Envoyé depuis mon mobile
- Reply message -
De : "Olivier Lamy"
Pour : "Maven Developers List"
Objet : svn commit: r843406 - in
+1
Envoyé depuis mon mobile
- Reply message -
De : "Simone Tripodi"
Pour : "Maven Developers List"
Objet : [VOTE] Release Apache Maven Fluido Skin 1.2 based on RC1
Date : lun., mars 19, 2012 11:18
Hi all guys,
I'm opening a thread vote today for releasing Apache Maven Fluido Skin
1.2,
For the main site, I worked with Joe: he incorporated site conventions to the
CMS web UI to offert online editing and publishing
Then extpaths.txt was added to let components sites published with svnpubsub
You have half of the story, I have the other one in site branch :)
Envoyé depuis mon mobi
