Hi,
Just updated with Felix's last commits (r1070751).
Site are now generated with 1.6-SNAPSHOT skin.
Are there any other changes for james-project before releasing 1.6?
Tks,
- Eric
On 9/03/2011 09:27, Norman Maurer wrote:
Looks like a left-over. "james-project" should be the correct one.
Bye,
Norman
2011/3/9 Felix Knecht<fel...@apache.org>
Ok. I also saw, that e.g. projects like mailbox have the james-server-root
as parent, but I couldn't find a technical reason for this. When e.g. using
james-project as parent it builds also. Do I miss something or is it
historically grown and maybe just a leftover?
Thanks
Felix
On 03/09/2011 09:13 AM, Norman Maurer wrote:
We should just release the parent if you think its ready...
Bye,
Norman
2011/3/9 Felix Knecht<fel...@apache.org>
On 03/09/2011 07:42 AM, Norman Maurer wrote:
We can use the SNAPSHOT until we make a release. For a release we MUST
NOT
depend on a SNAPSHOT.
I know, but this means either a) releasing e.g. james-server-root before
releasing mailbox or b) switch back to non SNAPSHOT version for releasing
and using an old parent.
Is it "common" to release also james-*-parent poms when doing a release
(sorry, probably a stupid question)?
Regards
Felix
Bye,
Norman
2011/3/9 Felix Knecht<fel...@apache.org>
On 03/08/2011 10:55 AM, Eric Charles wrote:
Hi Felix,
-site.xml descriptor is now installed.
mvn site on james-mailbox still uses 1.5 (not 1.6-SNAPSHOT).
Can version 1.6-SNAPSHOT be used instead of 1.5 in the parent
section?
What's the policy you use in this case for SNAPSHOTs for parent poms?
Regards
Felix
Can you build with 1.6-SNAPSHOT after deleting your local 1.6-SNAPSHOT
local repo?
Tks,
- Eric
On 8/03/2011 10:20, Felix Knecht wrote:
Hi Eric
Sorry, I was not complete when saying that maven didn't install the
snapshots.
Yes, m3 downloads the snapshots, but if you install if from you
local
PC
with "mvn install" to your local repo, it does not install the
*-site.xml needed to build the sites that inherites (the menus,...).
It's a bit complicated to explain, but if you look at
https://repository.apache.org/content/groups/snapshots/org/apache/james/james-project/1.6-SNAPSHOT/
you will see untill Sat Mar 05 some james-project-...-site.xml.
After, there are no more james-project-...-site.xml because of a m3
bug
(I suppose).
Maybe it's a feature? If I understand you right this [1] could be
the
problem and the solution.
Does adding the attach-descriptor goal solves the problem you're
talking about?
Thanks
Felix
[1]
https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+Compatibility+Notes#Maven3.xCompatibilityNotes-SiteandReporting
The consequence is that when I build the sites (mailbox, imap,...)
on
my
PC, it uses the 1.5 skin, and not the 1.6-SNAPSHOT one.
We could look if this is really a mvn bug, if a jira is open,...
As temporary fix, we could build the james-project project under m2,
which should fix the -site.xml deployment.
Tks,
- Eric
On 7/03/2011 16:30, Felix Knecht wrote:
Hi Eric
I temporary can't resolve a dependency from my location. I will
try
later...
However, I remember I had issue with maven 3 beta that didn't
install
the snapshots skins in local repo.
Is it still the case with 3.0.2 (snapshots will be resolved, but
I'm
curious to know if you had issues installing local skins) ?
I removed maven-skin from local repository (rm -rf
~/.m2/repository/org/apache/james/maven-skin/) and run the mvn site
-Psite-reports in the protocols project. The maven-skin got
downloaded, installed to local repo and used.
Technical reports may still have some inherited menus. This is the
case when the project's parent (pom.xml) is of version 1.5 and not
of
version 1.6-SNAPSHOT. I haven't changed them because I'm not up to
date about your policy using SNAPSHOTs in this place. In common
it's
not state of the art to use SNAPSHOTs.
Regards
Felix
Tks,
Eric
On 6/03/2011 06:33, Eric Charles wrote:
Hi Felix.
Great work!
I will update and try the generation with the new profile on my
laptop.
Tks,
Eric
On 5/03/2011 20:14, Felix Knecht wrote:
A short status update:
I reviewed following projects, put them to work using maven 3,
have
them prerequisiting mvn-3.0.2, make choosable if to generate
documentation (mvn site as before) or to generate technical
reports
(mvn site -Psite-reports):
- imap (imap-trunk-m2
- mailbox (
- mailbox-integration-tester
- protocols
- server
On Jenkins CI I changed configuration for these projects to use
maven
3 (latest) and generate the site. Technical reports are
available
via
Jenkins entering the project (Maven-generated site) or via
following
Url pattern:
https://hudson.apache.org/hudson/view/G-L/view/James/job/[imap-trunk-m2|mailbox|mailbox-integration-tests|protocols-trunk|james-server-trunk]/site
I'm aware of the not working banner images in the technical
reports.
Regards
Felix
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail:
server-dev-h...@james.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail:
server-dev-h...@james.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
