Re: APTEditor + Doxia

2007-07-26 Thread Trygve Laugstøl

Lukas Theussl wrote:



Vincent Siveton wrote:

Hi Math!

I recently add a pointer on your tool, so I am aware about your tool.

2007/7/25, Mathieu Avoine [EMAIL PROTECTED]:


Hi everyone,

I'm developing an Eclipse plugin called APT Editor which, like its name
suggests, is an editor/viewer for APT files. Basically, it offers an 
edit
pane to update the contents of the document, and a view pane to 
preview

the formatted version of the document in HTML.



It is a great tool for dev. We could have a live renderer.


The project page is http://apteditor.sf.net

Some people asked me if it was possible to offer the possibility to use
Maven Doxia's parser/renderer instead of the original code from pixware.
Sounds like a good idea to me, however not being a Doxia developer 
(not even

a Maven user to be honest) I wouldn't know where to look.

I'd appreciate if someone could give me some pointers as to how I could
integrate Doxia with the APT Editor. To summarize, I'd need to know what
libraries to load and what methods to invoke to generate an HTML 
version of

a given APT file into a chosen directory.



First, I suggest you to do a smart co of the doxia site
http://svn.apache.org/repos/asf/maven/doxia/site
We added lot of documentations these days.


Would be nice if we could publish the new docs already (for people who 
are not familiar with maven to build the site themselves), at least 
somewhere on a stage site, or even live, since the main site is just 
user docs. WDYT?




And another co from the full doxia project

The apt parser is here:
https://svn.apache.org/repos/asf/maven/doxia/doxia/trunk/doxia-modules/doxia-module-apt 



Another link that might be useful is Trygve's doxia-editor:

https://svn.apache.org/repos/asf/maven/sandbox/trunk/doxia/doxia-editor/

It's still in the sandbox and not very much advanced (it currently only 
does apt - xdoc conversion, and that not correctly... :( ), but from 
what I understand, it's supposed to be a stand-alone editor/renderer for 
any doxia-supported format.


The biggest problem with creating an editor for Doxia is that Doxia has 
no object model, it is all about events which is a major PITA. The only 
thing that is usable from the editor I made is the stuff that builds the 
objects.


--
Trygve


Announcing Mavenizer 1.0.0-alpha-1

2007-07-26 Thread Cédric Vidal
Hi Guys,

I would like to announce a new Apache licensed Maven 2 related tool called
Mavenizer:
http://mavenizer.sourceforge.net/

I've been heavily using Maven for a long time and just couldn't live without
it ;) but I often have to use third party libraries which have not been
mavenized already or simply have bad repository metadata. Either way,
mavenizing such libraries is a real pain especially when you want to get
Maven 2 transitive dependencies right.

Mavenizer attempts to ease the process of mavenizing such third party
libraries by trying to do as much guess work as possible.

A flash demo is available here, it illustrates the mavenization of
JFreeReport 0.8.7:
http://mavenizer.sourceforge.net/demos/jfreereport-0.8.7.html

This is considered alpha software. Nothing is stable yet; the code is pretty
monolithic and not pluggable at all. I plan on rewriting the code base from
the ground up in a more pluggable way so that Mavenizer can be extended with
user custom logic, naming strategies, etc ... But I wanted to release the
codebase as is as a proof of concept and why not, it could be helpful
already ;)

Any feedback on the way you use it and successful mavenizations using
Mavenizer would be really appreciated :) as well as bugs of course ^^ 

Kind regards,

Cédric Vidal

PS: Mavenizer is not related to Maveniser (with an 's' and also on
sourceforge), too bad the names are so close :(



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: svn commit: r559221 - /maven/site/trunk/src/site/apt/users/getting-help.apt

2007-07-26 Thread Dennis Lundberg
My plan was to add a link in the menu under User Centre and on the 
page http://maven.apache.org/users/index.html


Renaming Getting Support to Getting Help in the menu sounds good as 
well. We can do both. Plus add an entry in the FAQ about it.


There is already links to mail-lists.html on this page.


Vincent Siveton wrote:

Hi Dennis,

Sounds very useful for users. Thanks!

My only comment is where to put a link! FAQ? Renamed the Getting
Support page to it, with a link to mail-lists.html?

Cheers,

Vincent

2007/7/24, [EMAIL PROTECTED] [EMAIL PROTECTED]:

Author: dennisl
Date: Tue Jul 24 14:22:55 2007
New Revision: 559221

URL: http://svn.apache.org/viewvc?view=revrev=559221
Log:
o First draft of a more user-oriented guide to how users can help us 
help them. Please comment on this.




[SNIP]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




--
Dennis Lundberg

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: APTEditor + Doxia

2007-07-26 Thread Mathieu Avoine

Thanks to all of you for the answers. Now more questions! ;)

I've been reading through some code in Doxia lately to understand how HTML
site generation is done, however foreign code is always hard to read and I
was hoping someone would digest it a little bit for me (like I always say,
saving time requires to be lazy :P).

What I need to know is if it's still possible to call a Driver to have the
contents generated in a given place? Let me explain. If I try to make a
parallel with what I have done with Pixware's parser to achieve my goal, I
only extended the class fr.pixware.apt.convert.Driver (
apteditor.drivers.APTEditorDriver) and called the appropriate method. A bit
of code explains always better, so take a look at the following link, on
line 200, this is where all the magic happens in APT Editor:

http://apteditor.cvs.sourceforge.net/apteditor/APTEditor/src/apteditor/editors/MultiPageEditor.java?revision=1.3view=markup

I wish I could do the same with Doxia and let it do the dirty work: finding
the css, figures and other, execute macros, etc, so I can concentrate on
adding nice features to the UI of APT Editor.

If anyone knows the answer let me know. In the mean time, I will have a look
at Trygve's code (thanks for the links by the way) to see how he's done it.
Trygve, if you want to contribute some code (in one way or the other) let me
know, I'm sure we can help each other, we seem to have the same goal!

Thanks,
Math

On 7/26/07, Trygve Laugstøl [EMAIL PROTECTED] wrote:


Lukas Theussl wrote:


 Vincent Siveton wrote:
 Hi Math!

 I recently add a pointer on your tool, so I am aware about your tool.

 2007/7/25, Mathieu Avoine [EMAIL PROTECTED]:

 Hi everyone,

 I'm developing an Eclipse plugin called APT Editor which, like its
name
 suggests, is an editor/viewer for APT files. Basically, it offers an
 edit
 pane to update the contents of the document, and a view pane to
 preview
 the formatted version of the document in HTML.


 It is a great tool for dev. We could have a live renderer.

 The project page is http://apteditor.sf.net

 Some people asked me if it was possible to offer the possibility to
use
 Maven Doxia's parser/renderer instead of the original code from
pixware.
 Sounds like a good idea to me, however not being a Doxia developer
 (not even
 a Maven user to be honest) I wouldn't know where to look.

 I'd appreciate if someone could give me some pointers as to how I
could
 integrate Doxia with the APT Editor. To summarize, I'd need to know
what
 libraries to load and what methods to invoke to generate an HTML
 version of
 a given APT file into a chosen directory.


 First, I suggest you to do a smart co of the doxia site
 http://svn.apache.org/repos/asf/maven/doxia/site
 We added lot of documentations these days.

 Would be nice if we could publish the new docs already (for people who
 are not familiar with maven to build the site themselves), at least
 somewhere on a stage site, or even live, since the main site is just
 user docs. WDYT?


 And another co from the full doxia project

 The apt parser is here:

https://svn.apache.org/repos/asf/maven/doxia/doxia/trunk/doxia-modules/doxia-module-apt


 Another link that might be useful is Trygve's doxia-editor:

 https://svn.apache.org/repos/asf/maven/sandbox/trunk/doxia/doxia-editor/

 It's still in the sandbox and not very much advanced (it currently only
 does apt - xdoc conversion, and that not correctly... :( ), but from
 what I understand, it's supposed to be a stand-alone editor/renderer for
 any doxia-supported format.

The biggest problem with creating an editor for Doxia is that Doxia has
no object model, it is all about events which is a major PITA. The only
thing that is usable from the editor I made is the stuff that builds the
objects.

--
Trygve



Running reactor builds with MavenProjectStub?

2007-07-26 Thread jallen

It's been a while since i coded up some worth while Junit Mojo tests but
after reading the wiki pages and mucking about with the
maven-javadoc-plugin/src/test/java source I'm all excited over what I can
now do without having to go the fork an external maven instance to test my
plugins.

However, despite seeing that i can inject reactor projects into my mojo
configuration before execution am i correct in thinking that If i want to do
proper reactor tests, where a mojo is run against each project in the
reactor it is best to use the invoker/verifier approach?

Thanks,

John
-- 
View this message in context: 
http://www.nabble.com/Running-reactor-builds-with-MavenProjectStub--tf4151025s177.html#a11808609
Sent from the Maven Developers mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [Reporting] UI via JasperReports

2007-07-26 Thread Maria Odea Ching

Ok, I'll take a look at it :)

Thanks,
Deng

Teody Cue Jr. wrote:

Hi Guys,

I've attached a couple of patches for this on MRM-329. :)
Comments are very much welcome...

-Teody



Maria Odea Ching wrote:

I don't really know about its licensing though..

-Deng

Brett Porter wrote:
Me too - 2 years ago, I did both the html paging, and emailing 
pdfs of the same thing, plus letting people write their own reports 
to run.


how does the licensing fit these days?

On 19/07/2007, at 12:53 PM, Maria Odea Ching wrote:

I had some experience with JasperReports and iReport. I'll be happy 
to help out, though I may have to polish up on that. It's been 2 
years since I last used it.


-Deng

Joakim Erdfelt wrote:
I'm about to integrate JasperReports into archiva for report 
presentation in archiva.


This will be a learning experience for me. I'd love to have some 
help with this effort.
Anyone here have any experience with JasperReports on webapps? 
(things like HTML output with paging)


- Joakim












Julia Antonova/Tumlare is out of the office.

2007-07-26 Thread Julia Antonova

I will be out of the office starting  18-07-2007 and will not return until
01-08-2007.

I will respond to your message when I return.
Pls. forward all messages to [EMAIL PROTECTED]

[jira] Subscription: Design Best Practices

2007-07-26 Thread jira
Issue Subscription
Filter: Design  Best Practices (32 issues)
Subscriber: mavendevlist


Key Summary
MNG-2184Possible problem with @aggregator and forked lifecycles
http://jira.codehaus.org/browse/MNG-2184
MNG-612 implement conflict resolution techniques
http://jira.codehaus.org/browse/MNG-612
MNG-1936pattern: for mojo parameters which have default values in the POM 
we need standard usage
http://jira.codehaus.org/browse/MNG-1936
MNG-1950Ability to introduce new lifecycles phases
http://jira.codehaus.org/browse/MNG-1950
MNG-2381improved control over the repositories in the POM
http://jira.codehaus.org/browse/MNG-2381
MNG-1381best practices: testing strategies
http://jira.codehaus.org/browse/MNG-1381
MNG-474 performance improvement for forked lifecycles
http://jira.codehaus.org/browse/MNG-474
MNG-2125[doc] when and how to define plugins in a pom
http://jira.codehaus.org/browse/MNG-2125
MNG-2584Rebuild on pom change
http://jira.codehaus.org/browse/MNG-2584
MNG-1931add a reportingManagement section
http://jira.codehaus.org/browse/MNG-1931
MNG-1563how to write integration tests
http://jira.codehaus.org/browse/MNG-1563
MNG-1867deprecate system scope, analyse other use cases
http://jira.codehaus.org/browse/MNG-1867
MNG-905 review clean repo install of m2 for download trimming
http://jira.codehaus.org/browse/MNG-905
MNG-1569Make build process info read-only to mojos, and provide mechanism 
for explicit out-params for mojos to declare
http://jira.codehaus.org/browse/MNG-1569
MNG-1885Uniquely identify modules by module name and version number
http://jira.codehaus.org/browse/MNG-1885
MNG-140 refactor maven-artifact
http://jira.codehaus.org/browse/MNG-140
MNG-139 server definitions should be reusable
http://jira.codehaus.org/browse/MNG-139
MNG-647 Allow Maven 2 to be monitored using JMX.
http://jira.codehaus.org/browse/MNG-647
MNG-125 guarded mojo execution
http://jira.codehaus.org/browse/MNG-125
MNG-868 Use uniform format for properties and other tags
http://jira.codehaus.org/browse/MNG-868
MNG-1441Starting thinking about a proper distributed repository mechanism a 
la CPAN
http://jira.codehaus.org/browse/MNG-1441
MNG-416 best practices:  multiple profile deployments
http://jira.codehaus.org/browse/MNG-416
MNG-1437How to make additions to the POM and have it be backward/forward 
compatible
http://jira.codehaus.org/browse/MNG-1437
MNG-657 possible chicken and egg problem with extensions
http://jira.codehaus.org/browse/MNG-657
MNG-1425best practices: the location of configuration files vs resources
http://jira.codehaus.org/browse/MNG-1425
MNG-1439Organization Object Model (OOM) 
http://jira.codehaus.org/browse/MNG-1439
MNG-1468best practices: version management in multi project builds
http://jira.codehaus.org/browse/MNG-1468
MNG-1463best practices: plugin inheritance for a multi project build
http://jira.codehaus.org/browse/MNG-1463
MNG-1423best practices: setting up multi-module build
http://jira.codehaus.org/browse/MNG-1423
MNG-1440Developer Object Model (DOM)
http://jira.codehaus.org/browse/MNG-1440
MNG-41  best practices: site management
http://jira.codehaus.org/browse/MNG-41
MNG-367 best practices: multi-user installation
http://jira.codehaus.org/browse/MNG-367


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



MRELEASE-261 - review from dev's

2007-07-26 Thread jallen

Those in the know re the release manager and plugin:

Could i get a quick peer review of the solution proposed in 

http://jira.codehaus.org/browse/MRELEASE-261

to confirm I havent missed anything fundamental before I go try and
implement with my release-3 based manager and plugin?

Thanks!

John

-- 
View this message in context: 
http://www.nabble.com/MRELEASE-261---review-from-dev%27s-tf4151022s177.html#a11808605
Sent from the Maven Developers mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: APTEditor + Doxia

2007-07-26 Thread Vincent Siveton
2007/7/26, Lukas Theussl [EMAIL PROTECTED]:


 Vincent Siveton wrote:
  Hi Math!
 
  I recently add a pointer on your tool, so I am aware about your tool.
 
  2007/7/25, Mathieu Avoine [EMAIL PROTECTED]:
 
  Hi everyone,
 
  I'm developing an Eclipse plugin called APT Editor which, like its name
  suggests, is an editor/viewer for APT files. Basically, it offers an
  edit
  pane to update the contents of the document, and a view pane to preview
  the formatted version of the document in HTML.
 
 
  It is a great tool for dev. We could have a live renderer.
 
  The project page is http://apteditor.sf.net
 
  Some people asked me if it was possible to offer the possibility to use
  Maven Doxia's parser/renderer instead of the original code from pixware.
  Sounds like a good idea to me, however not being a Doxia developer
  (not even
  a Maven user to be honest) I wouldn't know where to look.
 
  I'd appreciate if someone could give me some pointers as to how I could
  integrate Doxia with the APT Editor. To summarize, I'd need to know what
  libraries to load and what methods to invoke to generate an HTML
  version of
  a given APT file into a chosen directory.
 
 
  First, I suggest you to do a smart co of the doxia site
  http://svn.apache.org/repos/asf/maven/doxia/site
  We added lot of documentations these days.

 Would be nice if we could publish the new docs already (for people who
 are not familiar with maven to build the site themselves), at least
 somewhere on a stage site, or even live, since the main site is just
 user docs. WDYT?

Done. Just waiting for sync.

Cheers,

Vincent


 
  And another co from the full doxia project
 
  The apt parser is here:
  https://svn.apache.org/repos/asf/maven/doxia/doxia/trunk/doxia-modules/doxia-module-apt

 Another link that might be useful is Trygve's doxia-editor:

 https://svn.apache.org/repos/asf/maven/sandbox/trunk/doxia/doxia-editor/

 It's still in the sandbox and not very much advanced (it currently only
 does apt - xdoc conversion, and that not correctly... :( ), but from
 what I understand, it's supposed to be a stand-alone editor/renderer for
 any doxia-supported format.


  FYI, Lukas started an issue to see the differences between pixware APT
  parser and doxia one: DOXIA-138

 Here's the full link, just in case ;)

 http://jira.codehaus.org/browse/DOXIA-138

 Cheers,
 -Lukas

 
  Cheers,
 
  Vincent
 
  Thanks for your help!
  Math