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
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 dependency.
My opinion, of course.
On Mon, Jul 18, 2011 at 3:38 AM, Lukas Theussl<[email protected]> wrote:
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
code. I would prefer to leave it that way for jxr.
-Lukas
On 07/17/2011 12:04 AM, Benson Margulies wrote:
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<[email protected]>
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 to 2.3? Or maybe you changed the
parent? We're a few working on site improvements to avoid regressions
with
future releases: site ITs have improved a lot recently, but we probably
still
need more experience
That's exaclty for this one that I proposed you to help: I'm on IRC,
don"t
hesitate to connect
Regards,
Hervé
Le samedi 16 juillet 2011, Benson Margulies a écrit :
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<[email protected]>
wrote:
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 would be cumbersome and more risky IMHO
don't hesitate to tell me if you want help to fix issues: for the
moment,
I'm not working on them to avoid checkin conflicts
Regards,
Hervé
Le samedi 16 juillet 2011, Benson Margulies a écrit :
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<[email protected]>
wrote:
+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 prevents plugin release, but these should be fixed when
the site is published
Regards,
Hervé
Le vendredi 15 juillet 2011, Benson Margulies a écrit :
Hi,
We solved 6 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?atl_token=ACIO-CAVI-
QX7 G-9
IAS|939d07db80126b429369a4acdb3a1c32519711ef|lin&version=16520&styleN
am e=Te xt&projectId=11085&Create=Create
There are still a gaggle of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&jqlQue
ry= pro
ject+%3D+JXR+AND+status+%3D+Open+ORDER+BY+priority+DESC&mode=hide
Staging repo:
https://repository.apache.org/content/repositories/maven-028/
Staging sites:
maven.apache.org/plugins/maven-jxr-plugin/staging
maven.apache.org/jxr/staging
Guide to testing staged releases:
http://maven.apache.org/guides/development/guide-testing-releases.htm
l
Vote open for at leasr 72 hours.
[ ] +1
[ ] +0
[ ] -1
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
