+1
On 7/15/11 1:05 PM, Benson Margulies wrote:
Hi,
We solved 6 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?atl_token=ACIO-CAVI-QX7G-9IAS|939d07db80126b429369a4acdb3a1c32519711ef|linversion=16520styleName=TextprojectId=11085Create=Create
There are still a gaggle of issues left in
+1
LieGrue,
strub
--- On Tue, 7/19/11, John Casey jdca...@commonjava.org wrote:
From: John Casey jdca...@commonjava.org
Subject: Re: [VOTE] Release Maven JXR version 2.3
To: Maven Developers List dev@maven.apache.org
Date: Tuesday, July 19, 2011, 3:05 PM
+1
On 7/15/11 1:05 PM, Benson
The vote has passed with the following results:
binding +1:
hboutemy
jdcasey
struberg
I will promote the artifacts to the central repo.
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands,
I think it is common usus in maven land to keep plugins inside their
respective projects (see eg maven-archetype-plugin,
maven-enforcer-plugin, maven-scm-plugin, maven-surefire-plugin,...), the
main advantage being that they are released together and kept in sync
and up-to date with the main
There's a lot of common stuff in the parent of the plugins:
announcements, changes, site config. Without mixins :-) we can't take
advantage of that. In short, I claim that the maven-jxr-plugin has
more in common with the rest of the plugins than it has with jxr. It's
only connection to JXR is one
an alternative is to give it maven-plugins as parent, but leave it
inside jxr, (like scm is doing). WDYT?
-Lukas
On 07/18/2011 02:50 PM, Benson Margulies wrote:
There's a lot of common stuff in the parent of the plugins:
announcements, changes, site config. Without mixins :-) we can't take
Sure.
On Mon, Jul 18, 2011 at 9:18 AM, Lukas Theussl ltheu...@apache.org wrote:
an alternative is to give it maven-plugins as parent, but leave it inside
jxr, (like scm is doing). WDYT?
-Lukas
On 07/18/2011 02:50 PM, Benson Margulies wrote:
There's a lot of common stuff in the parent of
Here's a dilemma. With -Preporting, I get the following when trying to
build both sites at the same time, since the plugin tries to use a jxr
report of itself. Maybe I just stick to one site at a time?
[ERROR] BUILD FAILURE
[INFO]
+1
tested in Maven 3.0.4-SNAPSHOT [1] (sync pending)
notice that there are some glitches with documentation:
- plugin-info.html isn't there nor goals documentation (?)
- aggregating example should be modified like javadoc to show new goals and
mark aggregate parameter as obsolete
nothing that
Hervé,
How can I make these site repairs when publishing against the label?
Is the idea to go ahead and make fixes to a checkout of the tag,
publish the site, and then patch them into trunk?
--benson
On Sat, Jul 16, 2011 at 5:06 AM, Hervé BOUTEMY herve.bout...@free.fr wrote:
+1
tested in
qhat I usually do is patch the trunk
and when publishing the final version, I copy modified files from site to my
local checkout
yes, that means that the site published on maven.apache.org isn't reproducible
But having a non-reproducible site isn't really an issue AFAIK
modifying the svn tag
By the way, is anyone still active who did the previous release of
JXR? It's not obvious how I could have caused these issues.
On Sat, Jul 16, 2011 at 3:36 PM, Hervé BOUTEMY herve.bout...@free.fr wrote:
qhat I usually do is patch the trunk
and when publishing the final version, I copy modified
for the old aggregation parameter, it's easy
for the goals documentation, yes, I don't understand how it can disappear. It
seems to be using m-site-p 2.2: upgrade to 2.3? Or maybe you changed the
parent? We're a few working on site improvements to avoid regressions with
future releases: site
I'll come looking for assistance once the vote passes.
On Sat, Jul 16, 2011 at 4:09 PM, Hervé BOUTEMY herve.bout...@free.fr wrote:
for the old aggregation parameter, it's easy
for the goals documentation, yes, I don't understand how it can disappear. It
seems to be using m-site-p 2.2: upgrade
For the next release, how would you feel about moving the plugin in
with the other plugins, and eliminating the extra level of parent?
On Sat, Jul 16, 2011 at 4:09 PM, Hervé BOUTEMY herve.bout...@free.fr wrote:
for the old aggregation parameter, it's easy
for the goals documentation, yes, I
Vincent S did a lot of work on JXR, and has a branch in sandbox
He's actually on holiday and should reply when he's back to make the good
choice
Regards,
Hervé
Le dimanche 17 juillet 2011, Benson Margulies a écrit :
For the next release, how would you feel about moving the plugin in
with the
Hi,
We solved 6 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?atl_token=ACIO-CAVI-QX7G-9IAS|939d07db80126b429369a4acdb3a1c32519711ef|linversion=16520styleName=TextprojectId=11085Create=Create
There are still a gaggle of issues left in JIRA:
17 matches
Mail list logo
