Re: Jelly tag for file content

[dion_gillard]

Check out the test cases I added to the eclipse plugin if this is what 
you're after...
--
dIon Gillard, Multitask Consulting



Miguel Griffa <[EMAIL PROTECTED]> wrote on 05/05/2004 03:44:52 PM:

> Hi all,
> Does anyone know how can I assert() that a file contains a given string 
> in jelly?
> 
> What I want to do is this:
> I have a test case and I want to ensure that the file contains a given 
> string somewhere
> 
> Thanks in advance
> 
> -- 
> 
> Miguel Griffa
> Software Architect
> Technisys.NET  "The First Digital e-nabler"
> Transactional Solutions
> 
> Miami +1 305 357 8109
> Madrid +34 915 726 763
> Buenos Aires: +54 11 43227100
> [EMAIL PROTECTED]
> http://www.technisys.net
> 
> 
> -
> 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]

RE: xdoc with custom templates and/or navigation

[dion_gillard]

What sort of custom menu layout did you produce?
--
dIon Gillard, Multitask Consulting



[EMAIL PROTECTED] wrote on 05/05/2004 10:49:09 PM:

> 
> Sorry but our firewall setup here does not allow us to use CVS on the
> internet (port blocked).
> I did it to get a custom menu layout.  Are there options to do this that 
I
> missed?
> 
> Regards,
> 
> Garvin LeClaire
> Anthem Inc.
> Senior Technical Architect
> Technology Architecture and Infrastructure
> Tel: 513-336-3305
> 
> 
> 
> 
>  
>   Brett Porter  
>   <[EMAIL PROTECTED]To:   "'Maven 
> Developers List'" <[EMAIL PROTECTED]> 
>   k.com.au>cc:  
>Subject:  RE: xdoc 
> with custom templates and/or navigation 
>   05/04/2004 08:07  
>   PM  
>   Please respond to  
>   "Maven Developers  
>   List"  
>  
>  
> 
> 
> 
> 
> The wiki has instructions on submitting patches.
> 
> You need to do cvs diff -u against CVS HEAD for maven-plugins/xdoc, ie:
> 
> 1. cvs checkout maven-plugins
> 2. make changes in xdoc plugin there
> 3. create issue in JIRA (MPXDOC- returned)
> 4. do this:
> cd maven-plugins
> cvs diff -u xdoc >MPXDOC-.diff
> 5. attach MPXDOC-.diff to the issue
> 6. wait for it to be applied
> 
> Remember to change  to the number given by JIRA.
> 
> But on a side note - I'm not exactly sure why you want to override 
these?
> 
> - Brett
> 
> 
> > -Original Message-
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> > Sent: Wednesday, 5 May 2004 6:50 AM
> > To: [EMAIL PROTECTED]
> > Subject: xdoc with custom templates and/or navigation
> >
> >
> > I have modified maven xdoc 1.6 to allow for the user to
> > override the templates or navigation menu.  I use xdoc1.6
> > that was included in the RC2
> > release.  I am not sure where to post these changes.   I have
> > include the
> > two files changed to make this work.
> > This give you the following new properties to control this:
> >maven.xdoc.templates
> >maven.xdoc.navigation
> > (See attached file: plugin.jelly)(See attached file:
> > plugin.properties) Regards, Garvin LeClaire Anthem Inc.
> > Senior Technical Architect Technology Architecture and Infrastructure
> > Tel: 513-336-3305
> > CONFIDENTIALITY NOTICE: This e-mail message, including any
> > attachments,
> > is for the sole use of the intended recipient(s) and may
> > contain confidential and privileged information or otherwise
> > protected by law.  Any unauthorized review, use, disclosure
> > or distribution is prohibited.  If you are not the intended
> > recipient, please contact the sender by reply e-mail and
> > destroy all copies of the original message.
> >
> 
> 
> 
> 
> 
> 
> 
> CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, 
> is for the sole use of the intended recipient(s) and may contain 
confidential
> and privileged information or otherwise protected by law.  Any 
unauthorized
> review, use, disclosure or distribution is prohibited.  If you are not 
the
> intended recipient, please contact the sender by reply e-mail and 
destroy
> all copies of the original message.
> 
> -
> 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]

[jira] Commented: (MAVEN-1271) "maven eclipse" can't find org.apache.commons.jelly.tags.xml.XMLTagLibrary

[jira]

The following comment has been added to this issue:

 Author: Christian Stein
Created: Thu, 6 May 2004 12:57 AM
   Body:
Why cactus? See excerpt from maven_-X_eclipse.txt:

[...]

Using projectPropertiesFile: 
...\.maven\plugins\cactus-maven-1.6dev-20040226\project.properties

Using projectBuildPropertiesFile: 
...\.maven\plugins\cactus-maven-1.6dev-20040226\build.properties

running script ...\.maven\plugins\cactus-mav
en-1.6dev-20040226\plugin.jelly

Processing dependencies for project Maven Cactus plugin; classloader 
[ForeheadClassLoader: name="root.maven"]

Non classpath dependency: 
'...\.maven\repository\maven\plugins\maven-ear-plugin-1.3.jar' not added to classpath

Non classpath dependency: 
'...\.maven\repository\maven\plugins\maven-ejb-plugin-1.2.jar' not added to classpath

Could not find the class: org.apache.commons.jelly.tags.xml.XMLTagLibrary

[...]
-
View this comment:
  
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1271&page=comments#action_19409

-
View the issue:
  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1271

Here is an overview of the issue:
-
Key: MAVEN-1271
Summary: "maven eclipse" can't find org.apache.commons.jelly.tags.xml.XMLTagLibrary
   Type: Bug

 Status: Unassigned
   Priority: Major

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

Project: maven
 Components: 
 jelly/ant integration
   Versions:
 1.0-rc2

   Assignee: 
   Reporter: Christian Stein

Created: Thu, 6 May 2004 12:43 AM
Updated: Thu, 6 May 2004 12:57 AM
Environment: Win2k
JRE 1.4.2_04
*clean/empty* Maven repo

Description:
See attached files for more console output. It seems to be a dependency problem with 
the cactus plugin.

This is, how I produce the error:

C:\>rmdir /S /Q "%HOME%\.maven"

C:\>mkdir "%HOME%\.maven"

C:\>mkdir "%HOME%\.maven\repository"

C:\>mkdir App

C:\>cd App

C:\App>maven genapp

[...]

C:\App>maven eclipse

[...]

Could not find the class: 
org.apache.commons.jelly.tags.xml.XMLTagLibrary

[...]


-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


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

[jira] Commented: (MAVEN-1216) NoClassDefFoundError for org/jaxen/JaxenException and org/saxpath/SAXPathException

[jira]

The following comment has been added to this issue:

 Author: Christian Stein
Created: Thu, 6 May 2004 12:52 AM
   Body:
Created an issue, as "my" problem differs from this one:

http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1271

-
View this comment:
  
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1216&page=comments#action_19408

-
View the issue:
  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1216

Here is an overview of the issue:
-
Key: MAVEN-1216
Summary: NoClassDefFoundError for org/jaxen/JaxenException  and 
org/saxpath/SAXPathException
   Type: Bug

 Status: Reopened
   Priority: Major

 Original Estimate: 1 hour
 Time Spent: Unknown
  Remaining: 1 hour

Project: maven
 Components: 
 jelly/ant integration
   Fix Fors:
 1.0-rc3
   Versions:
 1.0-rc2

   Assignee: Brett Porter
   Reporter: Vladimir Kralik

Created: Thu, 1 Apr 2004 9:51 AM
Updated: Thu, 6 May 2004 12:52 AM
Environment: maven-1.0-rc2
jdk 1.4.2_03
M$ Windows 2000 SP 4
cygwin

Description:
When I try install my own plugin ( by using "maven plugin:install" ),then I get :
<>
Caused by: java.lang.NoClassDefFoundError: org/jaxen/JaxenException
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:141)
at 
org.apache.commons.jelly.tags.xml.XMLTagLibrary.class$(XMLTagLibrary.java:82)
<>

after "cp jaxen-core-1.0-FCS.jar $MAVEN_HOME/lib" :

<>
Caused by: java.lang.NoClassDefFoundError: org/saxpath/SAXPathException
<>>
at 
org.apache.commons.jelly.tags.xml.XMLTagLibrary.class$(XMLTagLibrary.java:82)
<>

after "cp saxpath-1.0-FCS.jar $MAVEN_HOME/lib"

it works fine.

jaxen and saxpath are not listed as dependecies in my plugin.
I use very simple Hello World plugin ( see below )

I thing that problem is in jelly-integration, because jelly 
(org.apache.commons.jelly.tags.xml.ForEachTag) requires org.jaxen.JaxenException and 
dom4j (org.dom4j.xpath.XPathPattern) requieres org.saxpath.SAXPathException.

===
project.xml
===


  3
  maven-hello-plugin
  Maven Hello World Plug-in
  1.0.0-SNAPSHOT
  
  

  
${basedir}

  plugin.jelly
  plugin.properties
  project.xml

  

  

===
plugin.jelly
===



Hello, ${maven.hello.world}


===
plugin.properties
===
maven.hello.world=World


-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


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

[jira] Updated: (MAVEN-1271) "maven eclipse" can't find org.apache.commons.jelly.tags.xml.XMLTagLibrary

[jira]

The following issue has been updated:

Updater: Christian Stein (mailto:[EMAIL PROTECTED])
   Date: Thu, 6 May 2004 12:46 AM
Comment:
Debugging console. (-X)
Changes:
 Attachment changed to maven_-X_eclipse.txt
-
For a full history of the issue, see:

  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1271&page=history

-
View the issue:
  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1271

Here is an overview of the issue:
-
Key: MAVEN-1271
Summary: "maven eclipse" can't find org.apache.commons.jelly.tags.xml.XMLTagLibrary
   Type: Bug

 Status: Unassigned
   Priority: Major

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

Project: maven
 Components: 
 jelly/ant integration
   Versions:
 1.0-rc2

   Assignee: 
   Reporter: Christian Stein

Created: Thu, 6 May 2004 12:43 AM
Updated: Thu, 6 May 2004 12:46 AM
Environment: Win2k
JRE 1.4.2_04
*clean/empty* Maven repo

Description:
See attached files for more console output. It seems to be a dependency problem with 
the cactus plugin.

This is, how I produce the error:

C:\>rmdir /S /Q "%HOME%\.maven"

C:\>mkdir "%HOME%\.maven"

C:\>mkdir "%HOME%\.maven\repository"

C:\>mkdir App

C:\>cd App

C:\App>maven genapp

[...]

C:\App>maven eclipse

[...]

Could not find the class: 
org.apache.commons.jelly.tags.xml.XMLTagLibrary

[...]


-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


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

[jira] Updated: (MAVEN-1271) "maven eclipse" can't find org.apache.commons.jelly.tags.xml.XMLTagLibrary

[jira]

The following issue has been updated:

Updater: Christian Stein (mailto:[EMAIL PROTECTED])
   Date: Thu, 6 May 2004 12:45 AM
Comment:
Complete console output.
Changes:
 Attachment changed to maven+eclipse.txt
-
For a full history of the issue, see:

  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1271&page=history

-
View the issue:
  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1271

Here is an overview of the issue:
-
Key: MAVEN-1271
Summary: "maven eclipse" can't find org.apache.commons.jelly.tags.xml.XMLTagLibrary
   Type: Bug

 Status: Unassigned
   Priority: Major

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

Project: maven
 Components: 
 jelly/ant integration
   Versions:
 1.0-rc2

   Assignee: 
   Reporter: Christian Stein

Created: Thu, 6 May 2004 12:43 AM
Updated: Thu, 6 May 2004 12:45 AM
Environment: Win2k
JRE 1.4.2_04
*clean/empty* Maven repo

Description:
See attached files for more console output. It seems to be a dependency problem with 
the cactus plugin.

This is, how I produce the error:

C:\>rmdir /S /Q "%HOME%\.maven"

C:\>mkdir "%HOME%\.maven"

C:\>mkdir "%HOME%\.maven\repository"

C:\>mkdir App

C:\>cd App

C:\App>maven genapp

[...]

C:\App>maven eclipse

[...]

Could not find the class: 
org.apache.commons.jelly.tags.xml.XMLTagLibrary

[...]


-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


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

[jira] Created: (MAVEN-1271) "maven eclipse" can't find org.apache.commons.jelly.tags.xml.XMLTagLibrary

[jira]

Message:

  A new issue has been created in JIRA.

-
View the issue:
  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1271

Here is an overview of the issue:
-
Key: MAVEN-1271
Summary: "maven eclipse" can't find org.apache.commons.jelly.tags.xml.XMLTagLibrary
   Type: Bug

 Status: Unassigned
   Priority: Major

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

Project: maven
 Components: 
 jelly/ant integration
   Versions:
 1.0-rc2

   Assignee: 
   Reporter: Christian Stein

Created: Thu, 6 May 2004 12:43 AM
Updated: Thu, 6 May 2004 12:43 AM
Environment: Win2k
JRE 1.4.2_04
*clean/empty* Maven repo

Description:
See attached files for more console output. It seems to be a dependency problem with 
the cactus plugin.

This is, how I produce the error:

C:\>rmdir /S /Q "%HOME%\.maven"

C:\>mkdir "%HOME%\.maven"

C:\>mkdir "%HOME%\.maven\repository"

C:\>mkdir App

C:\>cd App

C:\App>maven genapp

[...]

C:\App>maven eclipse

[...]

Could not find the class: 
org.apache.commons.jelly.tags.xml.XMLTagLibrary

[...]


-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


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

[jira] Commented: (MPCHANGELOG-38) changelog does not work with cvsnt

[jira]

The following comment has been added to this issue:

 Author: dion gillard
Created: Wed, 5 May 2004 9:58 PM
   Body:
Can you run

maven -X maven-changelog-plugin:report

and post the output?
-
View this comment:
  
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPCHANGELOG-38&page=comments#action_19404

-
View the issue:
  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPCHANGELOG-38

Here is an overview of the issue:
-
Key: MPCHANGELOG-38
Summary: changelog does not work with cvsnt
   Type: Bug

 Status: Unassigned
   Priority: Major

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

Project: maven-changelog-plugin
   Versions:
 1.5

   Assignee: 
   Reporter: Archimedes Trajano

Created: Tue, 4 May 2004 1:35 PM
Updated: Wed, 5 May 2004 9:58 PM
Environment: CVSNT 2.0.26

Description:
C:\Projects\pensions>maven maven-changelog-plugin:report
 __  __
|  \/  |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \  ~ intelligent projects ~
|_|  |_\__,_|\_/\___|_||_|  v. 1.0-rc3-SNAPSHOT

build:start:

maven-changelog-plugin:report:
[echo] Generating the changelog report
Server is not supporting gzip-file-contents request
ChangeLog found: 0 entries
BUILD SUCCESSFUL
Total time: 5 seconds
Finished at: Tue May 04 19:27:12 CEST 2004



-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


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

[jira] Commented: (MPCHANGELOG-38) changelog does not work with cvsnt

[jira]

The following comment has been added to this issue:

 Author: dion gillard
Created: Wed, 5 May 2004 9:57 PM
   Body:
BTW, the changelog plugin does NOT use your installed client to perform CVS 
operations. So any issues with the CVSNT client are irrelevant
-
View this comment:
  
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPCHANGELOG-38&page=comments#action_19403

-
View the issue:
  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPCHANGELOG-38

Here is an overview of the issue:
-
Key: MPCHANGELOG-38
Summary: changelog does not work with cvsnt
   Type: Bug

 Status: Unassigned
   Priority: Major

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

Project: maven-changelog-plugin
   Versions:
 1.5

   Assignee: 
   Reporter: Archimedes Trajano

Created: Tue, 4 May 2004 1:35 PM
Updated: Wed, 5 May 2004 9:57 PM
Environment: CVSNT 2.0.26

Description:
C:\Projects\pensions>maven maven-changelog-plugin:report
 __  __
|  \/  |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \  ~ intelligent projects ~
|_|  |_\__,_|\_/\___|_||_|  v. 1.0-rc3-SNAPSHOT

build:start:

maven-changelog-plugin:report:
[echo] Generating the changelog report
Server is not supporting gzip-file-contents request
ChangeLog found: 0 entries
BUILD SUCCESSFUL
Total time: 5 seconds
Finished at: Tue May 04 19:27:12 CEST 2004



-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


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

[jira] Commented: (MPCHANGELOG-38) changelog does not work with cvsnt

[jira]

The following comment has been added to this issue:

 Author: dion gillard
Created: Wed, 5 May 2004 9:56 PM
   Body:
I fixed the documented goals
-
View this comment:
  
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPCHANGELOG-38&page=comments#action_19402

-
View the issue:
  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPCHANGELOG-38

Here is an overview of the issue:
-
Key: MPCHANGELOG-38
Summary: changelog does not work with cvsnt
   Type: Bug

 Status: Unassigned
   Priority: Major

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

Project: maven-changelog-plugin
   Versions:
 1.5

   Assignee: 
   Reporter: Archimedes Trajano

Created: Tue, 4 May 2004 1:35 PM
Updated: Wed, 5 May 2004 9:56 PM
Environment: CVSNT 2.0.26

Description:
C:\Projects\pensions>maven maven-changelog-plugin:report
 __  __
|  \/  |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \  ~ intelligent projects ~
|_|  |_\__,_|\_/\___|_||_|  v. 1.0-rc3-SNAPSHOT

build:start:

maven-changelog-plugin:report:
[echo] Generating the changelog report
Server is not supporting gzip-file-contents request
ChangeLog found: 0 entries
BUILD SUCCESSFUL
Total time: 5 seconds
Finished at: Tue May 04 19:27:12 CEST 2004



-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


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

cvs commit: maven-plugins/changelog/xdocs goals.xml changes.xml

[dion]

dion2004/05/05 18:56:05

  Modified:changelog/xdocs goals.xml changes.xml
  Log:
  Fix bad goals documentation
  
  Revision  ChangesPath
  1.3   +23 -7 maven-plugins/changelog/xdocs/goals.xml
  
  Index: goals.xml
  ===
  RCS file: /home/cvs/maven-plugins/changelog/xdocs/goals.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- goals.xml 4 Mar 2004 18:01:12 -   1.2
  +++ goals.xml 6 May 2004 01:56:05 -   1.3
  @@ -29,18 +29,34 @@
 
   GoalDescription
   
  -  changelog
  +  maven-changelog-plugin:report
 
  -This is the default goal of the plugin and simply attains
  -the changelog:generate goal.
  +Generates a report from the source control system showing
  +changes by date along with the message, if any, provided
  +by the developer when making the change
 
   
   
  -  changelog:generate
  +  changelog:create-cvspass
 
  -Generates a report from the source control system showing
  -changes by date along with the message, if any, provided
  -by the developer when making the change
  +A utility goal to set the cvs password for your project so that
  +the changelog plugin can authenticate. This is used mainly by CVSNT
  +users. The password file (.cvspass) is generated in the 
${user.home}
  +directory.
  +  
  +
  +
  +  maven-changelog-plugin:register
  +  
  +The standard goal name for report plugins to register themselves
  +with the site plugin.
  +  
  +
  +
  +  maven-changelog-plugin:deregister
  +  
  +The standard goal name for report plugins to deregister themselves
  +from the site.
 
   
 
  
  
  
  1.28  +1 -0  maven-plugins/changelog/xdocs/changes.xml
  
  Index: changes.xml
  ===
  RCS file: /home/cvs/maven-plugins/changelog/xdocs/changes.xml,v
  retrieving revision 1.27
  retrieving revision 1.28
  diff -u -r1.27 -r1.28
  --- changes.xml   29 Apr 2004 05:01:03 -  1.27
  +++ changes.xml   6 May 2004 01:56:05 -   1.28
  @@ -26,6 +26,7 @@
 
 
   
  +  Bad documentation 
for goals
 
   Add changelog:create-cvspass goal for creating the required .cvspass file
   Add documentation on .cvspass file for CVSNT users.
  
  
  

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

[jira] Commented: (MPCHANGELOG-38) changelog does not work with cvsnt

[jira]

The following comment has been added to this issue:

 Author: dion gillard
Created: Wed, 5 May 2004 9:49 PM
   Body:
create-cvspass creates the file where the changelog plugin expects it, in 
${user.home}. That's the point of it.

If you want to create it somewhere else, use maven.xml and the ant task.
-
View this comment:
  
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPCHANGELOG-38&page=comments#action_19401

-
View the issue:
  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPCHANGELOG-38

Here is an overview of the issue:
-
Key: MPCHANGELOG-38
Summary: changelog does not work with cvsnt
   Type: Bug

 Status: Unassigned
   Priority: Major

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

Project: maven-changelog-plugin
   Versions:
 1.5

   Assignee: 
   Reporter: Archimedes Trajano

Created: Tue, 4 May 2004 1:35 PM
Updated: Wed, 5 May 2004 9:49 PM
Environment: CVSNT 2.0.26

Description:
C:\Projects\pensions>maven maven-changelog-plugin:report
 __  __
|  \/  |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \  ~ intelligent projects ~
|_|  |_\__,_|\_/\___|_||_|  v. 1.0-rc3-SNAPSHOT

build:start:

maven-changelog-plugin:report:
[echo] Generating the changelog report
Server is not supporting gzip-file-contents request
ChangeLog found: 0 entries
BUILD SUCCESSFUL
Total time: 5 seconds
Finished at: Tue May 04 19:27:12 CEST 2004



-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


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

cvs commit: maven-plugins/plugin plugin.jelly

[dion]

dion2004/05/05 18:14:20

  Modified:plugin   plugin.jelly
  Log:
  Fix comments about expected attributes
  
  Revision  ChangesPath
  1.36  +1 -1  maven-plugins/plugin/plugin.jelly
  
  Index: plugin.jelly
  ===
  RCS file: /home/cvs/maven-plugins/plugin/plugin.jelly,v
  retrieving revision 1.35
  retrieving revision 1.36
  diff -u -r1.35 -r1.36
  --- plugin.jelly  28 Apr 2004 03:33:50 -  1.35
  +++ plugin.jelly  6 May 2004 01:14:20 -   1.36
  @@ -308,7 +308,7 @@
   
   
 
  -  
  +  
 
 
   Expected [${expected}] but got [${value}].${msg}
  
  
  

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

[jira] Commented: (MPECLIPSE-25) Add the capability of specifying more builders

[jira]

The following comment has been added to this issue:

 Author: dion gillard
Created: Wed, 5 May 2004 8:18 PM
   Body:
Thanks for the tests. I can add some checks on the xml similar to the tests in the ear 
plugin.
-
View this comment:
  
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPECLIPSE-25&page=comments#action_19399

-
View the issue:
  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPECLIPSE-25

Here is an overview of the issue:
-
Key: MPECLIPSE-25
Summary: Add the capability of specifying more builders
   Type: Improvement

 Status: Unassigned
   Priority: Major

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

Project: maven-eclipse-plugin

   Assignee: 
   Reporter: Miguel Griffa

Created: Mon, 3 May 2004 6:28 PM
Updated: Wed, 5 May 2004 8:18 PM

Description:
If the project uses any builder besidesd the java buidler the .project file cannot be 
generated. a property holding different builders and maybe natures would help solving 
this issue


-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


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

cvs commit: maven-components/maven-plugins/maven-idea-plugin/src/main/java/org/apache/maven/plugin IdeaWriter.java IdeaPlugin.java

[jvanzyl]

jvanzyl 2004/05/05 17:19:41

  Modified:maven-plugins/maven-idea-plugin/src/main/java/org/apache/maven/plugin
IdeaPlugin.java
  Added:   maven-plugins/maven-idea-plugin/src/main/java/org/apache/maven/plugin
IdeaWriter.java
  Log:
  
  
  Revision  ChangesPath
  1.5   +21 -242   
maven-components/maven-plugins/maven-idea-plugin/src/main/java/org/apache/maven/plugin/IdeaPlugin.java
  
  Index: IdeaPlugin.java
  ===
  RCS file: 
/home/cvs/maven-components/maven-plugins/maven-idea-plugin/src/main/java/org/apache/maven/plugin/IdeaPlugin.java,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- IdeaPlugin.java   5 May 2004 22:56:58 -   1.4
  +++ IdeaPlugin.java   6 May 2004 00:19:41 -   1.5
  @@ -1,261 +1,40 @@
   package org.apache.maven.plugin;
   
  -import org.apache.maven.artifact.MavenArtifact;
   import org.apache.maven.project.MavenProject;
  -import org.apache.maven.xdoc.render.DefaultXMLWriter;
  -import org.apache.maven.xdoc.render.XMLWriter;
  -import org.codehaus.plexus.util.InterpolationFilterReader;
  -
  -import java.io.File;
  -import java.io.FileWriter;
  -import java.io.InputStream;
  -import java.io.InputStreamReader;
  -import java.io.Writer;
  -import java.util.HashMap;
  -import java.util.Map;
   
   public class IdeaPlugin
   extends AbstractPlugin
   {
  -public void execute( PluginExecutionRequest request, PluginExecutionResponse 
response )
  -throws Exception
  -{
  -MavenProject project = (MavenProject) request.getParameter( "project" );
  -
  -File basedir = project.getFile().getParentFile();
  -
  -Map map = new HashMap();
  +protected IdeaWriter ideaWriter;
   
  -map.put( "project.artifactId", project.getArtifactId() );
  -
  -writeIdeaModule( basedir, project, map );
  -
  -writeIdeaWorkSpace( basedir, project, map );
  -
  -writeIdeaProject( basedir, project, map );
  -}
  -
  -// --
  -// IDEA project
  -// --
  -
  -private void writeIdeaProject( File basedir, MavenProject project, Map map )
  -throws Exception
  -{
  -copy( IdeaPlugin.class.getResourceAsStream( 
"/plugin-resources/default/idea.ipr" ),
  -  new FileWriter( new File( basedir, project.getArtifactId() + ".ipr" ) 
),
  -  map );
  -}
  -
  -// --
  -// IDEA workspace
  -// --
  -
  -private void writeIdeaWorkSpace( File basedir, MavenProject project, Map map )
  -throws Exception
  +public IdeaPlugin()
   {
  -copy( IdeaPlugin.class.getResourceAsStream( 
"/plugin-resources/default/idea.iws" ),
  -  new FileWriter( new File( basedir, project.getArtifactId() + ".iws" ) 
),
  -  map );
  +ideaWriter = new IdeaWriter();
   }
   
   // --
  -// IDEA module
  +// Now even in the context of a reactor, different things may be required:
  +//
  +// o you may actually want to generate complete ipr/iws/iml files for each
  +//   project that is picked up by the reactor.
  +//
  +// o you may want to generate the ipr/iws files for the top-level project and
  +//   only create iml files for each of the nested projects.
  +//
  +// Or the ipr/iws/iml files could be generated for each regardless but 
aggregated
  +// in a top-level project. This probably won't cause any harm as it will allow 
each
  +// project to be open individually or by the aggregated project with the child 
iml
  +// files. Most probably wouldn't use both modes but this is more akin to what 
might
  +// happen with a report vis-a-vis aggregation at the top-level.
  +//
  +// Here we go ...
   // --
   
  -private void writeIdeaModule( File basedir, MavenProject project, Map map )
  -throws Exception
  -{
  -FileWriter w = new FileWriter( new File( basedir, project.getArtifactId() + 
".iml" ) );
  -
  -XMLWriter writer = new DefaultXMLWriter( w );
  -
  -writer.startElement( "module" );
  -
  -writer.addAttribute( "version", "4" );
  -
  -writer.addAttribute( "relativePaths", "false" );
  -
  -writer.startElement( "component" );
  -
  -writer.addAttribute( "name", "ModuleRootManager" );
  -
  -writer.endElement();
  -
  -writer.startElement( "component" );
  -
  -writer.addAttribute( "name", "NewMod

RE: xdoc with custom templates and/or navigation

[Jason van Zyl]

On Wed, 2004-05-05 at 19:46, Brett Porter wrote:
> Fair enough, so all that is needed is a way to register/deregister your xdoc
> -> xhtml handler as part of the site plugin, for example.

Yes the site plugin, or something akin to it will handled all the
optional munging and various hooks. I myself have started writing
documentation in the APT format (http://www.xmlmind.com/aptconvert.html)
and this stuff gets converted to xdoc. So there can be multiple input
sources -> xdoc and from there no reason why we can't have multiple
output sources. I figured most wouldn't really care but very simple to
do. I planned on pluggable inputs and outputs are just as easy.

> - Brett
> 
> > -Original Message-
> > From: Jason van Zyl [mailto:[EMAIL PROTECTED] 
> > Sent: Thursday, 6 May 2004 9:40 AM
> > To: Maven Developers List
> > Subject: RE: xdoc with custom templates and/or navigation
> > 
> > 
> > On Wed, 2004-05-05 at 19:18, Brett Porter wrote:
> > > I'm a little confused on this thread. The fast xdoc plugins sounds 
> > > good and using *Mesh sounds like a neat idea, but I still don't 
> > > understand why we need things to conform to a certain XHTML output 
> > > format.
> > > 
> > > Surely the inputs are the page body (xdoc), the navigation 
> > (xml), and 
> > > perhaps some other metadata files we have come up with 
> > along the way, 
> > > and any plugins should work with that transforming xdoc -> 
> > xdoc, with 
> > > the actualy xdoc -> xhtml being the last stage of the pipeline?
> > > 
> > > And the xdoc plugin, while it should have a fast, standard 
> > > implementation, should definitely be able to read an XSLT 
> > file and use 
> > > that instead if that is what the user really wants to do.
> > 
> > That can be an add-on, something that won't go in xdoc 
> > plugin. If someone wants to munge the xdoc into some other 
> > xhtml format so that they can use a custom css then they can 
> > do that outside the xdoc plugin.
> > 
> > The xdoc plugin creates xhtml from the xdoc format so that it 
> > conforms to the css provided by the xdoc plugin. But there is 
> > no reason someone couldn't make a component that took the 
> > xdoc and performed an xslt transformation to produce a 
> > different xhtml format which was then styled by a custom css.
> > 
> > All the navigation, header, footer and body elements produced 
> > by the xdoc are rendered in certain format so they can be 
> > rendered with the supplied css. The new xdoc plugin performs 
> > a relatively simple task 
> > 
> > > That's my understanding, let me know if I'm missing something.
> > 
> > > Cheers,
> > > Brett
> > > 
> > > > -Original Message-
> > > > From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> > > > Sent: Wednesday, 5 May 2004 10:24 PM
> > > > To: Maven Developers List
> > > > Subject: RE: xdoc with custom templates and/or navigation
> > > > 
> > > > 
> > > > On Wed, 2004-05-05 at 04:38, Maczka Michal wrote:
> > > > 
> > > > > Jason!
> > > > > 
> > > > > 
> > > > > It's not just a question of the "theme".
> > > > > Some organization have already their own standards which define
> > > > > precisly how their intranet pages are looking. Often thy 
> > > > have alredy
> > > > > hundreds of pages with spcific layout which is 
> > completly different
> > > > > then this one which proposed by maven (for example some 
> > of them are 
> > > > > using html frames) For them it might not only be attrative 
> > > > but simply
> > > > > necessry to have much higher level of customization which
> > > > will allow
> > > > > to generate what they want.
> > > > 
> > > > That's fine, they can use tools like StaticMesh or SiteMesh
> > > > alter anything they like, or integrate whatever portions of 
> > > > the maven generated sites they like.
> > > > 
> > > > > I understand that you intention is to have quite simillar
> > > > (standard)
> > > > > sites which are easy to browse. It's an appealing goal 
> > but I think
> > > > > that most of the users will use the default theme 
> > anyway. But if 
> > > > > somebody cannot do this or he does not want he should  be 
> > > > free to go
> > > > > with his own solution.
> > > > 
> > > > They can, it's just not something I want baked in. I also say
> > > > this because the new xdoc plugin is blindingly fast because 
> > > > I'm directly writing out the xhtml from xml by passing the 
> > > > use of any other tools which is why it is so fast and so 
> > > > small. This is I will not sacrifice for users every whim for 
> > > > customization. This level of customization is entirely, and 
> > > > easily possibly with the StaticMesh/SiteMesh tools.
> > > > 
> > > > > BTW: in maven1 there are strange relations between site and xdoc
> > > > > plugins. We might imagine that somebody will be able to 
> > > > write his own
> > > > > replecment for xdoc plugin and use it from site plugin.
> > > > 
> > > > Yes, but ultimately the must conform to the xdoc style of
> > > > document or they basically get no bene

RE: xdoc with custom templates and/or navigation

[Brett Porter]

Fair enough, so all that is needed is a way to register/deregister your xdoc
-> xhtml handler as part of the site plugin, for example.

- Brett

> -Original Message-
> From: Jason van Zyl [mailto:[EMAIL PROTECTED] 
> Sent: Thursday, 6 May 2004 9:40 AM
> To: Maven Developers List
> Subject: RE: xdoc with custom templates and/or navigation
> 
> 
> On Wed, 2004-05-05 at 19:18, Brett Porter wrote:
> > I'm a little confused on this thread. The fast xdoc plugins sounds 
> > good and using *Mesh sounds like a neat idea, but I still don't 
> > understand why we need things to conform to a certain XHTML output 
> > format.
> > 
> > Surely the inputs are the page body (xdoc), the navigation 
> (xml), and 
> > perhaps some other metadata files we have come up with 
> along the way, 
> > and any plugins should work with that transforming xdoc -> 
> xdoc, with 
> > the actualy xdoc -> xhtml being the last stage of the pipeline?
> > 
> > And the xdoc plugin, while it should have a fast, standard 
> > implementation, should definitely be able to read an XSLT 
> file and use 
> > that instead if that is what the user really wants to do.
> 
> That can be an add-on, something that won't go in xdoc 
> plugin. If someone wants to munge the xdoc into some other 
> xhtml format so that they can use a custom css then they can 
> do that outside the xdoc plugin.
> 
> The xdoc plugin creates xhtml from the xdoc format so that it 
> conforms to the css provided by the xdoc plugin. But there is 
> no reason someone couldn't make a component that took the 
> xdoc and performed an xslt transformation to produce a 
> different xhtml format which was then styled by a custom css.
> 
> All the navigation, header, footer and body elements produced 
> by the xdoc are rendered in certain format so they can be 
> rendered with the supplied css. The new xdoc plugin performs 
> a relatively simple task 
> 
> > That's my understanding, let me know if I'm missing something.
> 
> > Cheers,
> > Brett
> > 
> > > -Original Message-
> > > From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> > > Sent: Wednesday, 5 May 2004 10:24 PM
> > > To: Maven Developers List
> > > Subject: RE: xdoc with custom templates and/or navigation
> > > 
> > > 
> > > On Wed, 2004-05-05 at 04:38, Maczka Michal wrote:
> > > 
> > > > Jason!
> > > > 
> > > > 
> > > > It's not just a question of the "theme".
> > > > Some organization have already their own standards which define
> > > > precisly how their intranet pages are looking. Often thy 
> > > have alredy
> > > > hundreds of pages with spcific layout which is 
> completly different
> > > > then this one which proposed by maven (for example some 
> of them are 
> > > > using html frames) For them it might not only be attrative 
> > > but simply
> > > > necessry to have much higher level of customization which
> > > will allow
> > > > to generate what they want.
> > > 
> > > That's fine, they can use tools like StaticMesh or SiteMesh
> > > alter anything they like, or integrate whatever portions of 
> > > the maven generated sites they like.
> > > 
> > > > I understand that you intention is to have quite simillar
> > > (standard)
> > > > sites which are easy to browse. It's an appealing goal 
> but I think
> > > > that most of the users will use the default theme 
> anyway. But if 
> > > > somebody cannot do this or he does not want he should  be 
> > > free to go
> > > > with his own solution.
> > > 
> > > They can, it's just not something I want baked in. I also say
> > > this because the new xdoc plugin is blindingly fast because 
> > > I'm directly writing out the xhtml from xml by passing the 
> > > use of any other tools which is why it is so fast and so 
> > > small. This is I will not sacrifice for users every whim for 
> > > customization. This level of customization is entirely, and 
> > > easily possibly with the StaticMesh/SiteMesh tools.
> > > 
> > > > BTW: in maven1 there are strange relations between site and xdoc
> > > > plugins. We might imagine that somebody will be able to 
> > > write his own
> > > > replecment for xdoc plugin and use it from site plugin.
> > > 
> > > Yes, but ultimately the must conform to the xdoc style of
> > > document or they basically get no benefit from any of the 
> > > plugins that produce the xdoc style. At any rate, these cases 
> > > will be few and far between and for those cases tools exist 
> > > to munge the generated xdoc or style xhtml in anyway 
> shape or form.
> > > 
> > > --
> > > jvz.
> > > 
> > > Jason van Zyl
> > > [EMAIL PROTECTED]
> > > http://maven.apache.org
> > > 
> > > happiness is like a butterfly: the more you chase it, the
> > > more it will elude you, but if you turn your attention to 
> > > other things, it will come and sit softly on your shoulder ...
> > > 
> > >  -- Thoreau
> > > 
> > > 
> > > 
> 
> > > -
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional

RE: xdoc with custom templates and/or navigation

[Jason van Zyl]

On Wed, 2004-05-05 at 19:18, Brett Porter wrote:
> I'm a little confused on this thread. The fast xdoc plugins sounds good and
> using *Mesh sounds like a neat idea, but I still don't understand why we
> need things to conform to a certain XHTML output format.
> 
> Surely the inputs are the page body (xdoc), the navigation (xml), and
> perhaps some other metadata files we have come up with along the way, and
> any plugins should work with that transforming xdoc -> xdoc, with the
> actualy xdoc -> xhtml being the last stage of the pipeline?
> 
> And the xdoc plugin, while it should have a fast, standard implementation,
> should definitely be able to read an XSLT file and use that instead if that
> is what the user really wants to do.

That can be an add-on, something that won't go in xdoc plugin. If
someone wants to munge the xdoc into some other xhtml format so that
they can use a custom css then they can do that outside the xdoc plugin.

The xdoc plugin creates xhtml from the xdoc format so that it conforms
to the css provided by the xdoc plugin. But there is no reason someone
couldn't make a component that took the xdoc and performed an xslt
transformation to produce a different xhtml format which was then styled
by a custom css.

All the navigation, header, footer and body elements produced by the
xdoc are rendered in certain format so they can be rendered with the
supplied css. The new xdoc plugin performs a relatively simple task 

> That's my understanding, let me know if I'm missing something.

> Cheers,
> Brett
> 
> > -Original Message-
> > From: Jason van Zyl [mailto:[EMAIL PROTECTED] 
> > Sent: Wednesday, 5 May 2004 10:24 PM
> > To: Maven Developers List
> > Subject: RE: xdoc with custom templates and/or navigation
> > 
> > 
> > On Wed, 2004-05-05 at 04:38, Maczka Michal wrote:
> > 
> > > Jason!
> > > 
> > > 
> > > It's not just a question of the "theme".
> > > Some organization have already their own standards which define 
> > > precisly how their intranet pages are looking. Often thy 
> > have alredy 
> > > hundreds of pages with spcific layout which is completly different 
> > > then this one which proposed by maven (for example some of them are 
> > > using html frames) For them it might not only be attrative 
> > but simply 
> > > necessry to have much higher level of customization which 
> > will allow 
> > > to generate what they want.
> > 
> > That's fine, they can use tools like StaticMesh or SiteMesh 
> > alter anything they like, or integrate whatever portions of 
> > the maven generated sites they like.
> > 
> > > I understand that you intention is to have quite simillar 
> > (standard) 
> > > sites which are easy to browse. It's an appealing goal but I think 
> > > that most of the users will use the default theme anyway. But if 
> > > somebody cannot do this or he does not want he should  be 
> > free to go 
> > > with his own solution.
> > 
> > They can, it's just not something I want baked in. I also say 
> > this because the new xdoc plugin is blindingly fast because 
> > I'm directly writing out the xhtml from xml by passing the 
> > use of any other tools which is why it is so fast and so 
> > small. This is I will not sacrifice for users every whim for 
> > customization. This level of customization is entirely, and 
> > easily possibly with the StaticMesh/SiteMesh tools.
> > 
> > > BTW: in maven1 there are strange relations between site and xdoc 
> > > plugins. We might imagine that somebody will be able to 
> > write his own 
> > > replecment for xdoc plugin and use it from site plugin.
> > 
> > Yes, but ultimately the must conform to the xdoc style of 
> > document or they basically get no benefit from any of the 
> > plugins that produce the xdoc style. At any rate, these cases 
> > will be few and far between and for those cases tools exist 
> > to munge the generated xdoc or style xhtml in anyway shape or form.
> > 
> > -- 
> > jvz.
> > 
> > Jason van Zyl
> > [EMAIL PROTECTED]
> > http://maven.apache.org
> > 
> > happiness is like a butterfly: the more you chase it, the 
> > more it will elude you, but if you turn your attention to 
> > other things, it will come and sit softly on your shoulder ...
> > 
> >  -- Thoreau 
> > 
> > 
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> > 

-- 
jvz.

Jason van Zyl
[EMAIL PROTECTED]
http://maven.apache.org

happiness is like a butterfly: the more you chase it, the more it will
elude you, but if you turn your attention to other things, it will come
and sit softly on your shoulder ...

 -- Thoreau 


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

RE: xdoc with custom templates and/or navigation

[Brett Porter]

I'm a little confused on this thread. The fast xdoc plugins sounds good and
using *Mesh sounds like a neat idea, but I still don't understand why we
need things to conform to a certain XHTML output format.

Surely the inputs are the page body (xdoc), the navigation (xml), and
perhaps some other metadata files we have come up with along the way, and
any plugins should work with that transforming xdoc -> xdoc, with the
actualy xdoc -> xhtml being the last stage of the pipeline?

And the xdoc plugin, while it should have a fast, standard implementation,
should definitely be able to read an XSLT file and use that instead if that
is what the user really wants to do.

That's my understanding, let me know if I'm missing something.

Cheers,
Brett

> -Original Message-
> From: Jason van Zyl [mailto:[EMAIL PROTECTED] 
> Sent: Wednesday, 5 May 2004 10:24 PM
> To: Maven Developers List
> Subject: RE: xdoc with custom templates and/or navigation
> 
> 
> On Wed, 2004-05-05 at 04:38, Maczka Michal wrote:
> 
> > Jason!
> > 
> > 
> > It's not just a question of the "theme".
> > Some organization have already their own standards which define 
> > precisly how their intranet pages are looking. Often thy 
> have alredy 
> > hundreds of pages with spcific layout which is completly different 
> > then this one which proposed by maven (for example some of them are 
> > using html frames) For them it might not only be attrative 
> but simply 
> > necessry to have much higher level of customization which 
> will allow 
> > to generate what they want.
> 
> That's fine, they can use tools like StaticMesh or SiteMesh 
> alter anything they like, or integrate whatever portions of 
> the maven generated sites they like.
> 
> > I understand that you intention is to have quite simillar 
> (standard) 
> > sites which are easy to browse. It's an appealing goal but I think 
> > that most of the users will use the default theme anyway. But if 
> > somebody cannot do this or he does not want he should  be 
> free to go 
> > with his own solution.
> 
> They can, it's just not something I want baked in. I also say 
> this because the new xdoc plugin is blindingly fast because 
> I'm directly writing out the xhtml from xml by passing the 
> use of any other tools which is why it is so fast and so 
> small. This is I will not sacrifice for users every whim for 
> customization. This level of customization is entirely, and 
> easily possibly with the StaticMesh/SiteMesh tools.
> 
> > BTW: in maven1 there are strange relations between site and xdoc 
> > plugins. We might imagine that somebody will be able to 
> write his own 
> > replecment for xdoc plugin and use it from site plugin.
> 
> Yes, but ultimately the must conform to the xdoc style of 
> document or they basically get no benefit from any of the 
> plugins that produce the xdoc style. At any rate, these cases 
> will be few and far between and for those cases tools exist 
> to munge the generated xdoc or style xhtml in anyway shape or form.
> 
> -- 
> jvz.
> 
> Jason van Zyl
> [EMAIL PROTECTED]
> http://maven.apache.org
> 
> happiness is like a butterfly: the more you chase it, the 
> more it will elude you, but if you turn your attention to 
> other things, it will come and sit softly on your shoulder ...
> 
>  -- Thoreau 
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 

RE: cvs commit: maven-components/maven-plugins/maven-idea-plugin - Imported sources

[Brett Porter]

Jason, should these plugins have their own package? Isn't
org.apache.maven.plugin going to hit a namespace conflict at some point?

- Brett

> -Original Message-
> From: Jason van Zyl [mailto:[EMAIL PROTECTED] 
> Sent: Thursday, 6 May 2004 6:46 AM
> To: Maven Developers List
> Subject: Re: cvs commit: 
> maven-components/maven-plugins/maven-idea-plugin - Imported sources
> 
> 
> On Wed, 2004-05-05 at 15:52, Emmanuel Venisse wrote:
> > Jason,
> > 
> > Could you do it more generic?
> > You hardcode the java version and sources directories. I 
> think isn't 
> > usable for future users.
> 
> Good eye, I whipped that one off quick. I took the source 
> directories from the model. For the java version I can just 
> grab the the java.version system property which will probably 
> be all right in most cases.
> 
> -- 
> jvz.
> 
> Jason van Zyl
> [EMAIL PROTECTED]
> http://maven.apache.org
> 
> happiness is like a butterfly: the more you chase it, the 
> more it will elude you, but if you turn your attention to 
> other things, it will come and sit softly on your shoulder ...
> 
>  -- Thoreau 
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 

[jira] Updated: (MAVEN-1270) multiproject:clean fails due to dependencies in reactor set

[jira]

The following issue has been updated:

Updater: Brett Porter (mailto:[EMAIL PROTECTED])
   Date: Wed, 5 May 2004 7:08 PM
Comment:
It's a good point, but it won't be fixed in 1.0 unfortunately
Changes:
 Fix Version changed to 1.1
-
For a full history of the issue, see:

  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1270&page=history

-
View the issue:
  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1270

Here is an overview of the issue:
-
Key: MAVEN-1270
Summary: multiproject:clean fails due to dependencies in reactor set
   Type: Improvement

 Status: Unassigned
   Priority: Minor

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

Project: maven
   Fix Fors:
 1.1
   Versions:
 1.0-rc2

   Assignee: 
   Reporter: Cameron Fieber

Created: Wed, 5 May 2004 2:18 PM
Updated: Wed, 5 May 2004 7:08 PM
Environment: RedHat 9.0. Sun JDK 1.4.2_01, Maven 1.0-rc2

Description:
I appologize if this is already entered, but I was unable to find it searching JIRA.  
This is the same as or similar to #MAVEN-443 which was marked as can't reproduce.

If you have a multiproject build, you can't execute clean until all artifacts in that 
build that depend on other artifacts in the build have been produced.

The ideal behaviour of multiproject:clean would be to either ignore dependencies not 
needed for the clean task itself, or consider a dependency satisfied if it is in the 
reactor set.

The case where this feature would be a particular benefit is when you have an existing 
source tree, which has been built, and a new component is added.  If you do an update 
and pulling down the new component it has yet to be compiled.  You then can't do 
multiproject:clean on your existing tree because the new dependencies to the new 
component can't be resolved.


-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


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

cvs commit: maven-components/maven-plugins/maven-idea-plugin/src/main/java/org/apache/maven/plugin IdeaPlugin.java

[jvanzyl]

jvanzyl 2004/05/05 15:56:58

  Modified:maven-plugins/maven-idea-plugin/src/main/java/org/apache/maven/plugin
IdeaPlugin.java
  Log:
  o cleaning up before writing out the project file using the xml writer in order to 
create a reactor aware mode that can write out multiple IDEA modules for an IDEA 
project where:
  IDEA module == Maven project
  
  Revision  ChangesPath
  1.4   +32 -28
maven-components/maven-plugins/maven-idea-plugin/src/main/java/org/apache/maven/plugin/IdeaPlugin.java
  
  Index: IdeaPlugin.java
  ===
  RCS file: 
/home/cvs/maven-components/maven-plugins/maven-idea-plugin/src/main/java/org/apache/maven/plugin/IdeaPlugin.java,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- IdeaPlugin.java   5 May 2004 20:51:03 -   1.3
  +++ IdeaPlugin.java   5 May 2004 22:56:58 -   1.4
  @@ -1,9 +1,9 @@
   package org.apache.maven.plugin;
   
  +import org.apache.maven.artifact.MavenArtifact;
   import org.apache.maven.project.MavenProject;
  -import org.apache.maven.xdoc.render.XMLWriter;
   import org.apache.maven.xdoc.render.DefaultXMLWriter;
  -import org.apache.maven.artifact.MavenArtifact;
  +import org.apache.maven.xdoc.render.XMLWriter;
   import org.codehaus.plexus.util.InterpolationFilterReader;
   
   import java.io.File;
  @@ -13,7 +13,6 @@
   import java.io.Writer;
   import java.util.HashMap;
   import java.util.Map;
  -import java.util.Iterator;
   
   public class IdeaPlugin
   extends AbstractPlugin
  @@ -29,42 +28,47 @@
   
   map.put( "project.artifactId", project.getArtifactId() );
   
  +writeIdeaModule( basedir, project, map );
  +
  +writeIdeaWorkSpace( basedir, project, map );
  +
  +writeIdeaProject( basedir, project, map );
  +}
  +
  +// --
  +// IDEA project
  +// --
  +
  +private void writeIdeaProject( File basedir, MavenProject project, Map map )
  +throws Exception
  +{
   copy( IdeaPlugin.class.getResourceAsStream( 
"/plugin-resources/default/idea.ipr" ),
 new FileWriter( new File( basedir, project.getArtifactId() + ".ipr" ) 
),
 map );
  +}
  +
  +// --
  +// IDEA workspace
  +// --
   
  +private void writeIdeaWorkSpace( File basedir, MavenProject project, Map map )
  +throws Exception
  +{
   copy( IdeaPlugin.class.getResourceAsStream( 
"/plugin-resources/default/idea.iws" ),
 new FileWriter( new File( basedir, project.getArtifactId() + ".iws" ) 
),
 map );
  +}
   
  +// --
  +// IDEA module
  +// --
  +
  +private void writeIdeaModule( File basedir, MavenProject project, Map map )
  +throws Exception
  +{
   FileWriter w = new FileWriter( new File( basedir, project.getArtifactId() + 
".iml" ) );
   
   XMLWriter writer = new DefaultXMLWriter( w );
  -
  -/*
  -
  -
  -  
  -  
  -
  -
  -  
  -  
  -
  -
  -
  -
  -  
  -
  -  
  -
  -
  -
  -  
  -
  -  
  -
  -*/
   
   writer.startElement( "module" );
   
  
  
  

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

[jira] Updated: (MPECLIPSE-10) added eclipseDependency='false' behavior

[jira]

The following issue has been updated:

Updater: thierry lach (mailto:[EMAIL PROTECTED])
   Date: Wed, 5 May 2004 4:53 PM
Comment:
Alternate patch.
Changes:
 Attachment changed to classpath.jelly.patch
-
For a full history of the issue, see:

  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPECLIPSE-10&page=history

-
View the issue:
  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPECLIPSE-10

Here is an overview of the issue:
-
Key: MPECLIPSE-10
Summary: added eclipseDependency='false' behavior
   Type: Improvement

 Status: Unassigned
   Priority: Minor

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

Project: maven-eclipse-plugin

   Assignee: 
   Reporter: Piotr Maj

Created: Fri, 22 Aug 2003 6:43 AM
Updated: Wed, 5 May 2004 4:53 PM
Environment: any

Description:
While generating .classpath file maven-eclipse-plugin includes all artifacts defined 
in project.xml regardless of it's type. As a side effect it may be observed that even 
JSP's *.tld files are included as Eclipse variables.It leads to project compile 
problems. Actually such project won't compile at all.

To avoid such behavior I propose a silly patch attached, which takes care of 
eclipseDependency property of artifacts. If it is set to 'false' the artifact will not 
be listed in .classpath.


-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


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

[jira] Commented: (MPECLIPSE-10) added eclipseDependency='false' behavior

[jira]

The following comment has been added to this issue:

 Author: thierry lach
Created: Wed, 5 May 2004 4:53 PM
   Body:
false could be useful to explicitly bypass 
specific jar files

My specific situation is that I am building a war file to run against an app server 
which is running on jdk 1.3, while eclipse is running against jdk 1.4.  Oracle 
requires two different jdbc driver jar files for jdk 1.3 and jdk 1.4.  I would want to 
tag the oracle-jdk13 jar file as war.bundle/true and eclipse.classpath/false, while 
not marking the oracle-jdk14 jar so it becomes part of the classpath.

I could use the same logic to address the jdk13/jdk14 xerces issues.


-
View this comment:
  
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPECLIPSE-10&page=comments#action_19394

-
View the issue:
  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPECLIPSE-10

Here is an overview of the issue:
-
Key: MPECLIPSE-10
Summary: added eclipseDependency='false' behavior
   Type: Improvement

 Status: Unassigned
   Priority: Minor

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

Project: maven-eclipse-plugin

   Assignee: 
   Reporter: Piotr Maj

Created: Fri, 22 Aug 2003 6:43 AM
Updated: Wed, 5 May 2004 4:53 PM
Environment: any

Description:
While generating .classpath file maven-eclipse-plugin includes all artifacts defined 
in project.xml regardless of it's type. As a side effect it may be observed that even 
JSP's *.tld files are included as Eclipse variables.It leads to project compile 
problems. Actually such project won't compile at all.

To avoid such behavior I propose a silly patch attached, which takes care of 
eclipseDependency property of artifacts. If it is set to 'false' the artifact will not 
be listed in .classpath.


-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


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

cvs commit: maven-components/maven-plugins/maven-idea-plugin/src/main/java/org/apache/maven/plugin IdeaPlugin.java

[jvanzyl]

jvanzyl 2004/05/05 13:51:03

  Modified:maven-plugins/maven-idea-plugin project.xml
   maven-plugins/maven-idea-plugin/src/main/java/org/apache/maven/plugin
IdeaPlugin.java
  Log:
  o use the java.version system property. i'm sure we could configure this in
other ways i.e. maybe accessing the list of available jvms from IDEA itself
but this will do for now.
  
  Revision  ChangesPath
  1.3   +5 -0  maven-components/maven-plugins/maven-idea-plugin/project.xml
  
  Index: project.xml
  ===
  RCS file: /home/cvs/maven-components/maven-plugins/maven-idea-plugin/project.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- project.xml   5 May 2004 20:33:30 -   1.2
  +++ project.xml   5 May 2004 20:51:03 -   1.3
  @@ -25,6 +25,11 @@
   
   
 maven
  +  maven-model
  +  2.0-SNAPSHOT
  +
  +
  +  maven
 maven-project
 2.0-SNAPSHOT
   
  
  
  
  1.3   +3 -1  
maven-components/maven-plugins/maven-idea-plugin/src/main/java/org/apache/maven/plugin/IdeaPlugin.java
  
  Index: IdeaPlugin.java
  ===
  RCS file: 
/home/cvs/maven-components/maven-plugins/maven-idea-plugin/src/main/java/org/apache/maven/plugin/IdeaPlugin.java,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- IdeaPlugin.java   5 May 2004 20:45:08 -   1.2
  +++ IdeaPlugin.java   5 May 2004 20:51:03 -   1.3
  @@ -132,7 +132,9 @@
   
   writer.addAttribute( "type", "jdk" );
   
  -writer.addAttribute( "jdkName", "java version "1.4.2"" );
  +String javaVersion = System.getProperty( "java.version" );
  +
  +writer.addAttribute( "jdkName", "java version " " + javaVersion + 
""" );
   
   writer.endElement();
   
  
  
  

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

Re: cvs commit: maven-components/maven-plugins/maven-idea-plugin - Imported sources

[Jason van Zyl]

On Wed, 2004-05-05 at 15:52, Emmanuel Venisse wrote:
> Jason,
> 
> Could you do it more generic?
> You hardcode the java version and sources directories. I think isn't usable
> for future users.

Good eye, I whipped that one off quick. I took the source directories
from the model. For the java version I can just grab the the
java.version system property which will probably be all right in most
cases.

-- 
jvz.

Jason van Zyl
[EMAIL PROTECTED]
http://maven.apache.org

happiness is like a butterfly: the more you chase it, the more it will
elude you, but if you turn your attention to other things, it will come
and sit softly on your shoulder ...

 -- Thoreau 


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

cvs commit: maven-components/maven-plugins/maven-idea-plugin/src/main/java/org/apache/maven/plugin IdeaPlugin.java

[jvanzyl]

jvanzyl 2004/05/05 13:45:08

  Modified:maven-plugins/maven-idea-plugin/src/main/java/org/apache/maven/plugin
IdeaPlugin.java
  Log:
  o take the source directories from the model. we want to use relative paths
so reach into the model for the unexpanded paths.
  
  Revision  ChangesPath
  1.2   +2 -2  
maven-components/maven-plugins/maven-idea-plugin/src/main/java/org/apache/maven/plugin/IdeaPlugin.java
  
  Index: IdeaPlugin.java
  ===
  RCS file: 
/home/cvs/maven-components/maven-plugins/maven-idea-plugin/src/main/java/org/apache/maven/plugin/IdeaPlugin.java,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- IdeaPlugin.java   5 May 2004 16:52:38 -   1.1
  +++ IdeaPlugin.java   5 May 2004 20:45:08 -   1.2
  @@ -100,7 +100,7 @@
   
   writer.startElement( "sourceFolder" );
   
  -writer.addAttribute( "url", "file://$MODULE_DIR$/src/main/java" );
  +writer.addAttribute( "url", "file://$MODULE_DIR$/" + 
project.getModel().getBuild().getSourceDirectory() );
   
   writer.addAttribute( "isTestSource", "false" );
   
  @@ -112,7 +112,7 @@
   
   writer.startElement( "sourceFolder" );
   
  -writer.addAttribute( "url", "file://$MODULE_DIR$/src/test/java" );
  +writer.addAttribute( "url", "file://$MODULE_DIR$/" + 
project.getModel().getBuild().getUnitTestSourceDirectory() );
   
   writer.addAttribute( "isTestSource", "true" );
   
  
  
  

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

cvs commit: maven-components/maven-plugins/maven-idea-plugin project.xml

[jvanzyl]

jvanzyl 2004/05/05 13:33:30

  Modified:maven-plugins/maven-idea-plugin project.xml
  Log:
  
  
  Revision  ChangesPath
  1.2   +0 -13 maven-components/maven-plugins/maven-idea-plugin/project.xml
  
  Index: project.xml
  ===
  RCS file: /home/cvs/maven-components/maven-plugins/maven-idea-plugin/project.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- project.xml   5 May 2004 16:52:38 -   1.1
  +++ project.xml   5 May 2004 20:33:30 -   1.2
  @@ -17,19 +17,6 @@
   scm:cvs:ext:[EMAIL 
PROTECTED]:/home/cvs:maven-components/maven-plugins/maven-scm-plugin
   http://cvs.apache.org/viewcvs.cgi/maven/
 
  -  
  -
  -  Emmanuel Venisse
  -  evenisse
  -  [EMAIL PROTECTED]
  -  
  -  
  -Creator
  -Project Leader
  -Release Manager
  -  
  -
  -  
 
   
 maven
  
  
  

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

Re: cvs commit: maven-components/maven-plugins/maven-idea-plugin - Imported sources

[Emmanuel Venisse]

Jason,

Could you do it more generic?
You hardcode the java version and sources directories. I think isn't usable
for future users.

Emmanuel

- Original Message - 
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, May 05, 2004 6:52 PM
Subject: cvs commit: maven-components/maven-plugins/maven-idea-plugin -
Imported sources


> jvanzyl 2004/05/05 09:52:40
>
>   Log:
>   o this won't be a core plugin but it is the first plugin that will be
> reactor aware and I need to be able to generate IDEA 4 project files
> to work :-)
>
> The modules for IDEA 4 map nicely to a nest hierarchy of maven
projects
> so I'm working on generating an IDEA project that consists of modules
> made up of all the maven projects found.
>
>   Status:
>
>   Vendor Tag: ASF
>   Release Tags: INIT
>
>   N maven-components/maven-plugins/maven-idea-plugin/.cvsignore
>   N maven-components/maven-plugins/maven-idea-plugin/project.xml
>   N
maven-components/maven-plugins/maven-idea-plugin/src/main/java/org/apache/ma
ven/plugin/IdeaPlugin.java
>   N
maven-components/maven-plugins/maven-idea-plugin/src/main/resources/META-INF
/maven/plugin.xml
>   N
maven-components/maven-plugins/maven-idea-plugin/src/main/resources/plugin-r
esources/default/idea.iml
>   N
maven-components/maven-plugins/maven-idea-plugin/src/main/resources/plugin-r
esources/default/idea.ipr
>   N
maven-components/maven-plugins/maven-idea-plugin/src/main/resources/plugin-r
esources/default/idea.iws
>
>   No conflicts created by this import
>
> -
> 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]

[jira] Commented: (MAVEN-1270) multiproject:clean fails due to dependencies in reactor set

[jira]

The following comment has been added to this issue:

 Author: Emmanuel Venisse
Created: Wed, 5 May 2004 3:28 PM
   Body:
OK, for resolve your problem, you can run :
maven -Dgoal=clean,jar:install multiproject:goal

this command line do a clean and a jar:install for each subproject, so your component 
will be install in your local repo.
-
View this comment:
  
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1270&page=comments#action_19392

-
View the issue:
  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1270

Here is an overview of the issue:
-
Key: MAVEN-1270
Summary: multiproject:clean fails due to dependencies in reactor set
   Type: Improvement

 Status: Unassigned
   Priority: Minor

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

Project: maven
   Versions:
 1.0-rc2

   Assignee: 
   Reporter: Cameron Fieber

Created: Wed, 5 May 2004 2:18 PM
Updated: Wed, 5 May 2004 3:28 PM
Environment: RedHat 9.0. Sun JDK 1.4.2_01, Maven 1.0-rc2

Description:
I appologize if this is already entered, but I was unable to find it searching JIRA.  
This is the same as or similar to #MAVEN-443 which was marked as can't reproduce.

If you have a multiproject build, you can't execute clean until all artifacts in that 
build that depend on other artifacts in the build have been produced.

The ideal behaviour of multiproject:clean would be to either ignore dependencies not 
needed for the clean task itself, or consider a dependency satisfied if it is in the 
reactor set.

The case where this feature would be a particular benefit is when you have an existing 
source tree, which has been built, and a new component is added.  If you do an update 
and pulling down the new component it has yet to be compiled.  You then can't do 
multiproject:clean on your existing tree because the new dependencies to the new 
component can't be resolved.


-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


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

Re: [jira] Commented: (MPECLIPSE-25) Add the capability of specifying more builders

[Miguel Griffa]

Hi
   I don't think (excuse me all for giving my opinion like this being 
so unknown) supporting eclipse plugins directy should be added to maven. 
This would be a lot of work and little payoff. I think that the current 
plugin shuold be improved to support all data for .project and 
.classpath (project references, sources locations) but nothing more. 
Plugins that use custom configuration files don't need anything more 
that a nature or builder (they can't need something unsupported by 
project description file).
  On the other side, a plugin that uses a custom confuiguration file, 
should support a configuration file generic enough to be on CVS and 
downloaded with the rest of the project. What would be the benefit of 
generating a file that could be on CVS?
property substitution and more could be done in a postGoal for eclise.
   Again, sorry for speaking wo loud, but I'm a big eclipse fan and I'm 
becoming a big maven fan too and, well...

Felipe Leme wrote:

Hi all,

Regardless of this patche fixing the bug or not, I think we could go a 
step further on the Eclipse project/nature/builder support. Let me 
explain better.

For the case of 'less intrusive' Eclipse plugins (like Checkstyle), I 
think the patch is fine. But that is not enough for plugins that takes 
more control of your eclipse workspace - there are some plugins, for 
instance, that creates some XML files or even copy other jars in your 
project. More than that, you might want to support multiple plugins in 
your project, according to each developer preference (or budget 
limitation).  Take for instance web/J2EE development. There are many 
plugins available for the task, being MyEclipseIDE and Lomboz the most 
popular ones. It would be nice if the same maven-powered project could 
be used by any of these plugins. So, in those cases, we would have 
specific goals for each plugin. Something like:

maven eclipse:eclipse -> default java project
maven eclispe:myeclipseide
maven eclipse:lomboz
and so on
We would still apply dion's patch so we can manually define our 
project builders, but when we call these new goals, the goal itself 
would know what builders/nature it must use.

Another thing that would be useful is to define the web structure of 
your application (i.e., where the files are, which JARs should be in 
the libetc...) in the POM, so these plugins could create the right 
structure in place (for instance, copying the jars from $MAVEN_HOME to 
web/WEB-INF/lib). But this is not specfic to the Eclipse plug-in, it 
should be something 'maven-widely' (maybe the current POM model 
already supports it - I'm still a semi-newbie maven user, so sorry if 
it already does and I didn't know :-).

Finally, once we discuss this issue and decide if it is usefull or not 
(i.e., if a new patch would be accepted/committed in), I could open a 
new bug describing it and even work on the patches (in fact, I should 
have done that already, but been too busy to - right now we are just 
using the default eclipse:eclise goal and then manually using 
MyEclipseIDE to add a web-module on the project).

Regards,

Felipe

[EMAIL PROTECTED] wrote:

The following comment has been added to this issue:

Author: dion gillard
   Created: Tue, 4 May 2004 9:04 PM
  Body:
This patch looks ok to me. It would be nice if we had a test case for 
it, but I can apply and test if everyone is ok with it

 

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


--

Miguel Griffa
Software Architect
Technisys.NET  "The First Digital e-nabler"
Transactional Solutions
Miami +1 305 357 8109
Madrid +34 915 726 763
Buenos Aires: +54 11 43227100
[EMAIL PROTECTED]
http://www.technisys.net
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Commented: (MAVEN-1270) multiproject:clean fails due to dependencies in reactor set

[jira]

The following comment has been added to this issue:

 Author: Cameron Fieber
Created: Wed, 5 May 2004 3:09 PM
   Body:
the structure is as you described in the first case, however the top level project.xml 
doesn't define any dependencies, it is just used to define the build structure, 
resources, repository, developers, and groupId.

here's what happens:

before:
root
|-project.xml - just global values, developers, etc but no dependencies
|-componentA
| |-api
| | |-project.xml (extends root project.xml)
| |-impl
| | |-project.xml (extends root project.xml, depends on
   componentA-api)

after (CVS update, someone added componentB, modified componentA-impl to use 
componentB):
root
|-project.xml - just global values, developers, etc but no
|   dependencies
|-componentA
| |-api
| | |-project.xml (extends root project.xml)
| |-impl
| | |-project.xml (extends root project.xml, depends on
|  componentA-api, componentB-api)
|-componentB
| |-api
| | |-project.xml (extends root project.xml)
| |-impl
| | |-project.xml (extends root project.xml, depends on
   componentB-api

What now happens, is that componentA has been built (has target directories), but you 
can't do a multiproject:clean because componentB-api hasn't been built yet and the 
multiproject:clean will detect the missing dependency for componentA-impl and fail.

-
View this comment:
  
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1270&page=comments#action_19391

-
View the issue:
  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1270

Here is an overview of the issue:
-
Key: MAVEN-1270
Summary: multiproject:clean fails due to dependencies in reactor set
   Type: Improvement

 Status: Unassigned
   Priority: Minor

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

Project: maven
   Versions:
 1.0-rc2

   Assignee: 
   Reporter: Cameron Fieber

Created: Wed, 5 May 2004 2:18 PM
Updated: Wed, 5 May 2004 3:09 PM
Environment: RedHat 9.0. Sun JDK 1.4.2_01, Maven 1.0-rc2

Description:
I appologize if this is already entered, but I was unable to find it searching JIRA.  
This is the same as or similar to #MAVEN-443 which was marked as can't reproduce.

If you have a multiproject build, you can't execute clean until all artifacts in that 
build that depend on other artifacts in the build have been produced.

The ideal behaviour of multiproject:clean would be to either ignore dependencies not 
needed for the clean task itself, or consider a dependency satisfied if it is in the 
reactor set.

The case where this feature would be a particular benefit is when you have an existing 
source tree, which has been built, and a new component is added.  If you do an update 
and pulling down the new component it has yet to be compiled.  You then can't do 
multiproject:clean on your existing tree because the new dependencies to the new 
component can't be resolved.


-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


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

[jira] Commented: (MAVEN-1270) multiproject:clean fails due to dependencies in reactor set

[jira]

The following comment has been added to this issue:

 Author: Emmanuel Venisse
Created: Wed, 5 May 2004 2:58 PM
   Body:
Oups sorry.

The best way is : 
root 
 |--project.xml (run multiproject from here, you don't need deps)) 
 |--master 
 | |--project.xml
 |--subproject1 
 | |--project.xml (extend on project.xml in master directory) 
 |--subproject2 
 | |--project.xml (extend on project.xml in master directory) 

Emmanuel

-
View this comment:
  
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1270&page=comments#action_19390

-
View the issue:
  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1270

Here is an overview of the issue:
-
Key: MAVEN-1270
Summary: multiproject:clean fails due to dependencies in reactor set
   Type: Improvement

 Status: Unassigned
   Priority: Minor

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

Project: maven
   Versions:
 1.0-rc2

   Assignee: 
   Reporter: Cameron Fieber

Created: Wed, 5 May 2004 2:18 PM
Updated: Wed, 5 May 2004 2:58 PM
Environment: RedHat 9.0. Sun JDK 1.4.2_01, Maven 1.0-rc2

Description:
I appologize if this is already entered, but I was unable to find it searching JIRA.  
This is the same as or similar to #MAVEN-443 which was marked as can't reproduce.

If you have a multiproject build, you can't execute clean until all artifacts in that 
build that depend on other artifacts in the build have been produced.

The ideal behaviour of multiproject:clean would be to either ignore dependencies not 
needed for the clean task itself, or consider a dependency satisfied if it is in the 
reactor set.

The case where this feature would be a particular benefit is when you have an existing 
source tree, which has been built, and a new component is added.  If you do an update 
and pulling down the new component it has yet to be compiled.  You then can't do 
multiproject:clean on your existing tree because the new dependencies to the new 
component can't be resolved.


-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


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

[jira] Commented: (MAVEN-1270) multiproject:clean fails due to dependencies in reactor set

[jira]

The following comment has been added to this issue:

 Author: Emmanuel Venisse
Created: Wed, 5 May 2004 2:49 PM
   Body:
I think the problem is :
This problem is due to a bad directory structure.

You merged the build process and the project definition in the same structure.
root
 |--project.xml (run multiproject from here)
 |--subproject1
 |   |--project.xml (extend on project.xml in parent directory)
 |--subproject2
 |   |--project.xml (extend on project.xml in parent directory)

Is it correct or similar?

The best way is :
root
 |--project.xml (run multiproject from here, you don't need deps))
 |--master
 |   |--project.xml (extend on project.xml in master directory)
 |--subproject1
 |   |--project.xml (extend on project.xml in master directory)
 |--subproject2
 |   |--project.xml (extend on project.xml in parent directory)


Emmanuel

-
View this comment:
  
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1270&page=comments#action_19389

-
View the issue:
  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1270

Here is an overview of the issue:
-
Key: MAVEN-1270
Summary: multiproject:clean fails due to dependencies in reactor set
   Type: Improvement

 Status: Unassigned
   Priority: Minor

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

Project: maven
   Versions:
 1.0-rc2

   Assignee: 
   Reporter: Cameron Fieber

Created: Wed, 5 May 2004 2:18 PM
Updated: Wed, 5 May 2004 2:49 PM
Environment: RedHat 9.0. Sun JDK 1.4.2_01, Maven 1.0-rc2

Description:
I appologize if this is already entered, but I was unable to find it searching JIRA.  
This is the same as or similar to #MAVEN-443 which was marked as can't reproduce.

If you have a multiproject build, you can't execute clean until all artifacts in that 
build that depend on other artifacts in the build have been produced.

The ideal behaviour of multiproject:clean would be to either ignore dependencies not 
needed for the clean task itself, or consider a dependency satisfied if it is in the 
reactor set.

The case where this feature would be a particular benefit is when you have an existing 
source tree, which has been built, and a new component is added.  If you do an update 
and pulling down the new component it has yet to be compiled.  You then can't do 
multiproject:clean on your existing tree because the new dependencies to the new 
component can't be resolved.


-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


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

Jelly tag for file content

[Miguel Griffa]

Hi all,
Does anyone know how can I assert() that a file contains a given string 
in jelly?

What I want to do is this:
I have a test case and I want to ensure that the file contains a given 
string somewhere

Thanks in advance

--

Miguel Griffa
Software Architect
Technisys.NET  "The First Digital e-nabler"
Transactional Solutions
Miami +1 305 357 8109
Madrid +34 915 726 763
Buenos Aires: +54 11 43227100
[EMAIL PROTECTED]
http://www.technisys.net
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Created: (MAVEN-1270) multiproject:clean fails due to dependencies in reactor set

[jira]

Message:

  A new issue has been created in JIRA.

-
View the issue:
  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1270

Here is an overview of the issue:
-
Key: MAVEN-1270
Summary: multiproject:clean fails due to dependencies in reactor set
   Type: Improvement

 Status: Unassigned
   Priority: Minor

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

Project: maven
   Versions:
 1.0-rc2

   Assignee: 
   Reporter: Cameron Fieber

Created: Wed, 5 May 2004 2:18 PM
Updated: Wed, 5 May 2004 2:18 PM
Environment: RedHat 9.0. Sun JDK 1.4.2_01, Maven 1.0-rc2

Description:
I appologize if this is already entered, but I was unable to find it searching JIRA.  
This is the same as or similar to #MAVEN-443 which was marked as can't reproduce.

If you have a multiproject build, you can't execute clean until all artifacts in that 
build that depend on other artifacts in the build have been produced.

The ideal behaviour of multiproject:clean would be to either ignore dependencies not 
needed for the clean task itself, or consider a dependency satisfied if it is in the 
reactor set.

The case where this feature would be a particular benefit is when you have an existing 
source tree, which has been built, and a new component is added.  If you do an update 
and pulling down the new component it has yet to be compiled.  You then can't do 
multiproject:clean on your existing tree because the new dependencies to the new 
component can't be resolved.


-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


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

Re: [jira] Commented: (MPECLIPSE-25) Add the capability of specifying more builders

[Miguel Griffa]

I submited a patch that adds tests for the builders and natures,
I made the tests separated because I think that the test shuold include 
some validation over the expected contents of the generated file
I don't know how to do this with jelly yet...

Miguel Griffa wrote:

I'll go for the test case now,
I'm sorry, but being newbie is a bit unfamiliar for me testing maven 
plugin
I'll submit a patch for the test case if I manage to get one :)

[EMAIL PROTECTED] wrote:

The following comment has been added to this issue:

Author: dion gillard
   Created: Tue, 4 May 2004 9:04 PM
  Body:
This patch looks ok to me. It would be nice if we had a test case for 
it, but I can apply and test if everyone is ok with it
-
View this comment:
 http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPECLIPSE-25&page=comments#action_19371 

-
View the issue:
 http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPECLIPSE-25
Here is an overview of the issue:
-
   Key: MPECLIPSE-25
   Summary: Add the capability of specifying more builders
  Type: Improvement
Status: Unassigned
  Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
 Remaining: Unknown
   Project: maven-eclipse-plugin

  Assignee:   Reporter: Miguel Griffa

   Created: Mon, 3 May 2004 6:28 PM
   Updated: Tue, 4 May 2004 9:04 PM
Description:
If the project uses any builder besidesd the java buidler the 
.project file cannot be generated. a property holding different 
builders and maybe natures would help solving this issue

-
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
  http://jira.codehaus.org/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
  http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
 





--

Miguel Griffa
Software Architect
Technisys.NET  "The First Digital e-nabler"
Transactional Solutions
Miami +1 305 357 8109
Madrid +34 915 726 763
Buenos Aires: +54 11 43227100
[EMAIL PROTECTED]
http://www.technisys.net
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (MPECLIPSE-25) Add the capability of specifying more builders

[jira]

The following issue has been updated:

Updater: Miguel Griffa (mailto:[EMAIL PROTECTED])
   Date: Wed, 5 May 2004 1:19 PM
Comment:
Adds tests for the functionallity of the previous patch
Changes:
 Attachment changed to test-patch.txt
-
For a full history of the issue, see:

  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPECLIPSE-25&page=history

-
View the issue:
  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPECLIPSE-25

Here is an overview of the issue:
-
Key: MPECLIPSE-25
Summary: Add the capability of specifying more builders
   Type: Improvement

 Status: Unassigned
   Priority: Major

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

Project: maven-eclipse-plugin

   Assignee: 
   Reporter: Miguel Griffa

Created: Mon, 3 May 2004 6:28 PM
Updated: Wed, 5 May 2004 1:19 PM

Description:
If the project uses any builder besidesd the java buidler the .project file cannot be 
generated. a property holding different builders and maybe natures would help solving 
this issue


-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


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

cvs commit: maven-components/maven-plugins/maven-idea-plugin - Imported sources

[jvanzyl]

jvanzyl 2004/05/05 09:52:40

  Log:
  o this won't be a core plugin but it is the first plugin that will be
reactor aware and I need to be able to generate IDEA 4 project files
to work :-)
  
The modules for IDEA 4 map nicely to a nest hierarchy of maven projects
so I'm working on generating an IDEA project that consists of modules
made up of all the maven projects found.
  
  Status:
  
  Vendor Tag:   ASF
  Release Tags: INIT
  
  N maven-components/maven-plugins/maven-idea-plugin/.cvsignore
  N maven-components/maven-plugins/maven-idea-plugin/project.xml
  N 
maven-components/maven-plugins/maven-idea-plugin/src/main/java/org/apache/maven/plugin/IdeaPlugin.java
  N 
maven-components/maven-plugins/maven-idea-plugin/src/main/resources/META-INF/maven/plugin.xml
  N 
maven-components/maven-plugins/maven-idea-plugin/src/main/resources/plugin-resources/default/idea.iml
  N 
maven-components/maven-plugins/maven-idea-plugin/src/main/resources/plugin-resources/default/idea.ipr
  N 
maven-components/maven-plugins/maven-idea-plugin/src/main/resources/plugin-resources/default/idea.iws
  
  No conflicts created by this import

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

Re: groups syncing to ibiblio

[Mark R. Diggory]

Mauro Talevi wrote:

Mark R. Diggory wrote:

No, you missunderstood me, we're not breaking up the repository, its 
still all one, just organizing it better for management purposes, the 
directory structure is not different virtual machines.

maven.ibibilio.org/apache/
maven.ibibilio.org/codehaus/
same thing as

www.ibibilio.org/maven/apache/
www.ibibilio.org/maven/codehaus/
Ultimately the issue here is in organization/group/artifact id's 
being more hierarchical, not separating out into separate repositories.


I undestand what you're saying, but from the point of view of the 
maven client these are two separate remote repos.

I saw the big advantage of ibiblio as being a source-agnostic
repository of projects artifacts with a flat structure.
Else you would need a "all others" organization level for projects
that don't fit into any other category.
I guess what I'm asking is if the benefits of the organizational 
structure are outweighted by the loss of simplicity and generality.


We are discussing the future Maven2 client/repository here, not the 
current client. In the future Repository URI syntax there is a 
positional space in the uri for "organization" so that the content can 
be organized by the following



Sorry if this caused confusion,
Mark


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

[jira] Commented: (MPMULTIPROJECT-24) goal 'site' fails with following : creation was not successful for an unknown reason

[jira]

The following comment has been added to this issue:

 Author: Archimedes Trajano
Created: Wed, 5 May 2004 12:03 PM
   Body:
Perhaps adding a schema check for the project.xml file will at least highlight that 
there is a problem with the file.
-
View this comment:
  
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPMULTIPROJECT-24&page=comments#action_19385

-
View the issue:
  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPMULTIPROJECT-24

Here is an overview of the issue:
-
Key: MPMULTIPROJECT-24
Summary: goal 'site' fails with following : creation was not successful for an 
unknown reason
   Type: Bug

 Status: Open
   Priority: Minor

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

Project: maven-multiproject-plugin

   Assignee: Brett Porter
   Reporter: Paul Spencer

Created: Mon, 12 Apr 2004 8:27 AM
Updated: Wed, 5 May 2004 12:03 PM
Environment: maven 1.0-rc2, Windows XP, Java 1.4

Description:
The multiproject:site goals was failing with following error:
creation was not successful for an unknown reason

After much looking around, I found the problem.  One of the project.xml files was a 
missing  tag in a project XML.

After adding the  tag to the project.xml, the goal succeeded! 


-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


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

[jira] Created: (MAVEN-1269) Add the capability to hide goal names from output

[jira]

Message:

  A new issue has been created in JIRA.

-
View the issue:
  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1269

Here is an overview of the issue:
-
Key: MAVEN-1269
Summary: Add the capability to hide goal names from output
   Type: Improvement

 Status: Unassigned
   Priority: Major

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

Project: maven
   Versions:
 1.0-rc3

   Assignee: 
   Reporter: Archimedes Trajano

Created: Wed, 5 May 2004 11:32 AM
Updated: Wed, 5 May 2004 11:32 AM

Description:
Just wondering if we can have a setting by default whereby certain goal names do not 
appear when you are running maven.  Especially the ones labeled :init it would at 
least make the run look cleaner.  Basically you can probably have it where 
undocumented goals or specially tagged goals have their names not displayed.


-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


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

RE: xdoc with custom templates and/or navigation

[Jason van Zyl]

On Wed, 2004-05-05 at 10:54, [EMAIL PROTECTED] wrote:
> I am trying to alter what is in the Navigation Menu.  I would like this to
> be controlled programmatically (Jelly script) to still have consistency
> with project sites generated.

I've added programmatic control to the new xdoc plugin so this type of
thing should be easier to do in the future.

> Regards,
> 
> Garvin LeClaire
> Anthem Inc.
> Senior Technical Architect
> Technology Architecture and Infrastructure
> Tel: 513-336-3305
> 
> 
> 
> 
>  
>   
>   Jason van Zyl  
>   
>   <[EMAIL PROTECTED]To:   Maven Developers List 
> <[EMAIL PROTECTED]>  
>   g>   cc:   
>   
>Subject:  RE: xdoc with custom 
> templates and/or navigation  
>   05/05/2004 10:30   
>   
>   AM 
>   
>   Please respond to  
>   
>   "Maven Developers  
>   
>   List"  
>   
>  
>   
>  
>   
> 
> 
> 
> 
> On Wed, 2004-05-05 at 08:53, [EMAIL PROTECTED] wrote:
> > Is there a recommended way to modify the navigation menu?
> 
> I don't know what you're trying to do. If you're changing the structure
> of the xhtml then you can take a look at:
> 
> http://www.pols.co.uk/downloads/static-mesh/
> 
> The primary goals of the new xdoc plugin are speed and efficient use of
> memory where themes are control entirely via css, not changing the
> structure of the output.
> 
> So using something like Jelly/JSL I'm not even vaguely considering
> because we can't even generate the plugin site without it crapping out.
> If there is something that is comensurable with the goals of speed and
> efficiency then I would incorporate it. There are some things that Joe
> Walnes is working on in XStream for doing XML transformations in an
> extremely efficient manner so that I would possibly incorporate.
> 
> Another option would be to use SiteMesh:
> 
> http://www.opensymphony.com/sitemesh/
> 
> If you are trying to incorporate a Maven site into your corporate
> website. A general tool could probably be made for this where all you
> would be responsible for is making a decorator to mutate the maven xhtml
> to whatever you need to display to make your pointy haired bosses happy.
> 
> 
> --
> jvz.
> 
> Jason van Zyl
> [EMAIL PROTECTED]
> http://maven.apache.org
> 
> happiness is like a butterfly: the more you chase it, the more it will
> elude you, but if you turn your attention to other things, it will come
> and sit softly on your shoulder ...
> 
>  -- Thoreau
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 
> 
> 
> 
> 
> 
> CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, 
> is for the sole use of the intended recipient(s) and may contain confidential
> and privileged information or otherwise protected by law.  Any unauthorized
> review, use, disclosure or distribution is prohibited.  If you are not the
> intended recipient, please contact the sender by reply e-mail and destroy
> all copies of the original message.
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]

-- 
jvz.

Jason van Zyl
[EMAIL PROTECTED]
http://maven.apache.org

happiness is like a butterfly: the more you chase it, the more it will
elude you, but if you turn your attention to other things, it will come
and sit softly on your shoulder ...

 -- Thoreau 


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

Re: groups syncing to ibiblio

[Mauro Talevi]

Mark R. Diggory wrote:

No, you missunderstood me, we're not breaking up the repository, its 
still all one, just organizing it better for management purposes, the 
directory structure is not different virtual machines.

maven.ibibilio.org/apache/
maven.ibibilio.org/codehaus/
same thing as

www.ibibilio.org/maven/apache/
www.ibibilio.org/maven/codehaus/
Ultimately the issue here is in organization/group/artifact id's being 
more hierarchical, not separating out into separate repositories.
I undestand what you're saying, but from the point of view of the maven 
client these are two separate remote repos.

I saw the big advantage of ibiblio as being a source-agnostic
repository of projects artifacts with a flat structure.
Else you would need a "all others" organization level for projects
that don't fit into any other category.
I guess what I'm asking is if the benefits of the organizational 
structure are outweighted by the loss of simplicity and generality.

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

RE: xdoc with custom templates and/or navigation

[Maczka Michal]

> -Original Message-
> From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, May 05, 2004 4:30 PM
> To: Maven Developers List
> Subject: RE: xdoc with custom templates and/or navigation
> 
> 
> On Wed, 2004-05-05 at 08:53, [EMAIL PROTECTED] wrote:
> > Is there a recommended way to modify the navigation menu?
> 
> I don't know what you're trying to do. If you're changing the 
> structure
> of the xhtml then you can take a look at:
> 
> http://www.pols.co.uk/downloads/static-mesh/
> 
> The primary goals of the new xdoc plugin are speed and 
> efficient use of
> memory where themes are control entirely via css, not changing the
> structure of the output.
> 

That's fine!

> So using something like Jelly/JSL I'm not even vaguely considering
> because we can't even generate the plugin site without it 
> crapping out.
> If there is something that is comensurable with the goals of speed and
> efficiency then I would incorporate it. There are some things that Joe
> Walnes is working on in XStream for doing XML transformations in an
> extremely efficient manner so that I would possibly incorporate.
> 


Jason why you are assuming that the only solution which will allow higher
degree of customisation  
is to make xdoc plugin configurable/customisable and template based? 

It's the site plugin which should be customisable and there you could be
able to choose how do you want to transform 
your xdocs.

AFAIK: SiteMesh and such tools are easy you use if you want to add some
things to pages. But they are not so easy to use 
when you want to remove parts of the pages. IMO it will be much simpler and
way faster to do xdoc2html or xdoc2flash thing then doing
xdoc2xhtml with your super fast xdoc plugin and then xhtml2html or
xhtml2flash with sitemesh

When maven will be based on plexus it will just mean that somebody should be
able to drop his component which will be used by site plugin
to perform xdoc transformation. It's not something more complex then that.
Optimised components are cool and we should promote this way of thinking.
But they are also very small classes which are super easy to rewrite and
first of all they are _components_!!. It means they are _replaceable_.
Why one should use things like sitemesh when he can quickly write his own
component which will be also optimised for speed, memory usage and
efficiency
and in addition will match requirements of this person or his organization.


Michal


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

RE: xdoc with custom templates and/or navigation

[Garvin . LeClaire]

I am trying to alter what is in the Navigation Menu.  I would like this to
be controlled programmatically (Jelly script) to still have consistency
with project sites generated.

Regards,

Garvin LeClaire
Anthem Inc.
Senior Technical Architect
Technology Architecture and Infrastructure
Tel: 513-336-3305




   

  Jason van Zyl

  <[EMAIL PROTECTED]To:   Maven Developers List 
<[EMAIL PROTECTED]>  
  g>   cc: 

   Subject:  RE: xdoc with custom 
templates and/or navigation  
  05/05/2004 10:30 

  AM   

  Please respond to

  "Maven Developers

  List"

   

   





On Wed, 2004-05-05 at 08:53, [EMAIL PROTECTED] wrote:
> Is there a recommended way to modify the navigation menu?

I don't know what you're trying to do. If you're changing the structure
of the xhtml then you can take a look at:

http://www.pols.co.uk/downloads/static-mesh/

The primary goals of the new xdoc plugin are speed and efficient use of
memory where themes are control entirely via css, not changing the
structure of the output.

So using something like Jelly/JSL I'm not even vaguely considering
because we can't even generate the plugin site without it crapping out.
If there is something that is comensurable with the goals of speed and
efficiency then I would incorporate it. There are some things that Joe
Walnes is working on in XStream for doing XML transformations in an
extremely efficient manner so that I would possibly incorporate.

Another option would be to use SiteMesh:

http://www.opensymphony.com/sitemesh/

If you are trying to incorporate a Maven site into your corporate
website. A general tool could probably be made for this where all you
would be responsible for is making a decorator to mutate the maven xhtml
to whatever you need to display to make your pointy haired bosses happy.


--
jvz.

Jason van Zyl
[EMAIL PROTECTED]
http://maven.apache.org

happiness is like a butterfly: the more you chase it, the more it will
elude you, but if you turn your attention to other things, it will come
and sit softly on your shoulder ...

 -- Thoreau


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








CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, 
is for the sole use of the intended recipient(s) and may contain confidential
and privileged information or otherwise protected by law.  Any unauthorized
review, use, disclosure or distribution is prohibited.  If you are not the
intended recipient, please contact the sender by reply e-mail and destroy
all copies of the original message.

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

RE: xdoc with custom templates and/or navigation

[Jason van Zyl]

On Wed, 2004-05-05 at 08:53, [EMAIL PROTECTED] wrote:
> Is there a recommended way to modify the navigation menu?

I don't know what you're trying to do. If you're changing the structure
of the xhtml then you can take a look at:

http://www.pols.co.uk/downloads/static-mesh/

The primary goals of the new xdoc plugin are speed and efficient use of
memory where themes are control entirely via css, not changing the
structure of the output.

So using something like Jelly/JSL I'm not even vaguely considering
because we can't even generate the plugin site without it crapping out.
If there is something that is comensurable with the goals of speed and
efficiency then I would incorporate it. There are some things that Joe
Walnes is working on in XStream for doing XML transformations in an
extremely efficient manner so that I would possibly incorporate.

Another option would be to use SiteMesh:

http://www.opensymphony.com/sitemesh/

If you are trying to incorporate a Maven site into your corporate
website. A general tool could probably be made for this where all you
would be responsible for is making a decorator to mutate the maven xhtml
to whatever you need to display to make your pointy haired bosses happy.


-- 
jvz.

Jason van Zyl
[EMAIL PROTECTED]
http://maven.apache.org

happiness is like a butterfly: the more you chase it, the more it will
elude you, but if you turn your attention to other things, it will come
and sit softly on your shoulder ...

 -- Thoreau 


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

Re: groups syncing to ibiblio

[Jason van Zyl]

On Wed, 2004-05-05 at 08:53, Mark R. Diggory wrote:

> I think its a great idea to have other organizations who wish to rsync 
> use the script. But this should be a decision within those groups, if 
> you are a member of that groups and you object, you should take it up 
> with that group. The rsync is a management tool to make the repository 
> managers jobs easier.

This is exactly the tact taken with the Codehaus artifacts. In this
particular case Maven is closely connected with Codehaus, but I still
discussed things with Bob (the codehaus despot) to arrange everything.

> The goal here is to build a stable and scalable repository of trusted 
> content, not to have a "anarchy" diskspace where you can't trust anyones 
> content. To do this requires stronger "institutional" management of the 
> larger groups like Apache, Codehaus etc. and the proper signing (both 
> md5 and pgp) of artifacts...

Having a sync from Codehaus would infact be a step in the right
direction.

> With this is mind, Jason, how close are we to having "hierarchical" 
> organization/group directories? My point is that it would be far easier 
> for us to control any overlap in projects if the organizations were 
> isolated into separate directories.
> 
> for instance
> 
> www.ibiblio.org/maven/apache/
> www.ibiblio.org/maven/codehaus/
> 
> also, is it possible to get virtual host names out of Ibiblio, ie
> 
> maven.ibiblio.org/apache/
> maven.ibiblio.org/codehaus/
> 
> Maybe this is something we can really push for version two, before there 
> are too many dependent projects?

It's one of the things on the list but will be more a requisite for the
first beta release of maven2. The first alpha will use the existing
format. It's really not a technical problem, more a matter of deciding
the format which will most likely come to the fore when the first alpha
of wagon goes out the door

-- 
jvz.

Jason van Zyl
[EMAIL PROTECTED]
http://maven.apache.org

happiness is like a butterfly: the more you chase it, the more it will
elude you, but if you turn your attention to other things, it will come
and sit softly on your shoulder ...

 -- Thoreau 


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

Re: [jira] Commented: (MPECLIPSE-25) Add the capability of specifying more builders

[Miguel Griffa]

I'll go for the test case now,
I'm sorry, but being newbie is a bit unfamiliar for me testing maven plugin
I'll submit a patch for the test case if I manage to get one :)
[EMAIL PROTECTED] wrote:

The following comment has been added to this issue:

Author: dion gillard
   Created: Tue, 4 May 2004 9:04 PM
  Body:
This patch looks ok to me. It would be nice if we had a test case for it, but I can 
apply and test if everyone is ok with it
-
View this comment:
 
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPECLIPSE-25&page=comments#action_19371
-
View the issue:
 http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPECLIPSE-25
Here is an overview of the issue:
-
   Key: MPECLIPSE-25
   Summary: Add the capability of specifying more builders
  Type: Improvement
Status: Unassigned
  Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
 Remaining: Unknown
   Project: maven-eclipse-plugin

  Assignee: 
  Reporter: Miguel Griffa

   Created: Mon, 3 May 2004 6:28 PM
   Updated: Tue, 4 May 2004 9:04 PM
Description:
If the project uses any builder besidesd the java buidler the .project file cannot be 
generated. a property holding different builders and maybe natures would help solving 
this issue
-
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
  http://jira.codehaus.org/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
  http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
 



--

Miguel Griffa
Software Architect
Technisys.NET  "The First Digital e-nabler"
Transactional Solutions
Miami +1 305 357 8109
Madrid +34 915 726 763
Buenos Aires: +54 11 43227100
[EMAIL PROTECTED]
http://www.technisys.net
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Commented: (MPCHANGELOG-31) Changelog does not work with cvs version 1.11.12

[jira]

The following comment has been added to this issue:

 Author: Archimedes Trajano
Created: Wed, 5 May 2004 9:35 AM
   Body:
I am not sure if it is because of the upgrade to 3.6 (I don't think it is since 
according to their issue log it fixes the problem that I am experiencing with CVSNT 
2.0, but it still does not work.

Anyway here's the bug report, in case you think it warrants another dependent bug 
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPCHANGELOG-38
-
View this comment:
  
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPCHANGELOG-31&page=comments#action_19383

-
View the issue:
  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPCHANGELOG-31

Here is an overview of the issue:
-
Key: MPCHANGELOG-31
Summary: Changelog does not work with cvs version 1.11.12
   Type: Bug

 Status: Closed
   Priority: Blocker
 Resolution: FIXED

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

Project: maven-changelog-plugin
   Fix Fors:
 1.5

   Assignee: Brett Porter
   Reporter: Maarten Coene

Created: Wed, 25 Feb 2004 6:18 PM
Updated: Wed, 5 May 2004 9:35 AM

Description:
Because of a bug in the netbeans cvslib library, changelog does not work with cvs 
version 1.11.12  This cvslib bug has been fixed recently, but this plugin still uses 
the old buggy cvslib jar.

More info about the cvslib bug: http://www.netbeans.org/issues/show_bug.cgi?id=39919




-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


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

Re: groups syncing to ibiblio

[Mark R. Diggory]

Mauro Talevi wrote:

Mark,

separating maven repositories by organizations sort of defeates the
point of putting them in a common unique place such as ibiblio.
That is, once could two different url, say
dist.apache.org
dist.codehaus.org
and those can be set on the client side as the maven repos
(this is done to access the codehaus.org jars currently)
The nice thing about the maven repository is that it agnostic of
the origin of the artifacts, it just cares about the name of the 
artifact group, ie the structure underneath ibiblio.org/maven.

That said, one could - for operational/organizational purposes -
have different upload areas for different orgs, but
then the artifacts themselves should really be put into a single repo.
Cheers,
Mauro
No, you missunderstood me, we're not breaking up the repository, its 
still all one, just organizing it better for management purposes, the 
directory structure is not different virtual machines.

maven.ibibilio.org/apache/
maven.ibibilio.org/codehaus/
same thing as

www.ibibilio.org/maven/apache/
www.ibibilio.org/maven/codehaus/
Ultimately the issue here is in organization/group/artifact id's being 
more hierarchical, not separating out into separate repositories.

--
Mark Diggory
Software Developer
Harvard MIT Data Center
http://www.hmdc.harvard.edu
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: groups syncing to ibiblio

[Mauro Talevi]

Mark R. Diggory wrote:
With this is mind, Jason, how close are we to having "hierarchical" 
organization/group directories? My point is that it would be far easier 
for us to control any overlap in projects if the organizations were 
isolated into separate directories.

for instance

www.ibiblio.org/maven/apache/
www.ibiblio.org/maven/codehaus/
also, is it possible to get virtual host names out of Ibiblio, ie

maven.ibiblio.org/apache/
maven.ibiblio.org/codehaus/
Maybe this is something we can really push for version two, before there 
are too many dependent projects?

Mark,

separating maven repositories by organizations sort of defeates the
point of putting them in a common unique place such as ibiblio.
That is, once could two different url, say
dist.apache.org
dist.codehaus.org
and those can be set on the client side as the maven repos
(this is done to access the codehaus.org jars currently)
The nice thing about the maven repository is that it agnostic of
the origin of the artifacts, it just cares about the name of the 
artifact group, ie the structure underneath ibiblio.org/maven.

That said, one could - for operational/organizational purposes -
have different upload areas for different orgs, but
then the artifacts themselves should really be put into a single repo.
Cheers,
Mauro
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: maven/maven-jelly-tags project.xml

[brett]

brett   2004/05/05 06:19:14

  Modified:maven-jelly-tags Tag: MAVEN-1_0-BRANCH project.xml
  Log:
  fix images
  
  Revision  ChangesPath
  No   revision
  No   revision
  1.1.2.5   +2 -2  maven/maven-jelly-tags/project.xml
  
  Index: project.xml
  ===
  RCS file: /home/cvs/maven/maven-jelly-tags/project.xml,v
  retrieving revision 1.1.2.4
  retrieving revision 1.1.2.5
  diff -u -r1.1.2.4 -r1.1.2.5
  --- project.xml   5 May 2004 07:27:57 -   1.1.2.4
  +++ project.xml   5 May 2004 13:19:14 -   1.1.2.5
  @@ -27,11 +27,11 @@
 
   Apache Software Foundation
   http://www.apache.org/
  -/images/apache-maven-project.png
  +http://maven.apache.org/images/apache-maven-project.png
 
 2001
 org.apache.maven.jelly.tags
  -  /images/maven.gif
  +  http://maven.apache.org/images/maven.gif
   
 
   The Maven jelly tag library is designed to be used in Maven Jelly scripts and 
plugins to perform
  
  
  

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

RE: xdoc with custom templates and/or navigation

[Garvin . LeClaire]

Sorry but our firewall setup here does not allow us to use CVS on the
internet (port blocked).
I did it to get a custom menu layout.  Are there options to do this that I
missed?

Regards,

Garvin LeClaire
Anthem Inc.
Senior Technical Architect
Technology Architecture and Infrastructure
Tel: 513-336-3305




   

  Brett Porter 

  <[EMAIL PROTECTED]To:   "'Maven Developers List'" 
<[EMAIL PROTECTED]>  
  k.com.au>cc: 

   Subject:  RE: xdoc with custom 
templates and/or navigation  
  05/04/2004 08:07 

  PM   

  Please respond to

  "Maven Developers

  List"

   

   





The wiki has instructions on submitting patches.

You need to do cvs diff -u against CVS HEAD for maven-plugins/xdoc, ie:

1. cvs checkout maven-plugins
2. make changes in xdoc plugin there
3. create issue in JIRA (MPXDOC- returned)
4. do this:
cd maven-plugins
cvs diff -u xdoc >MPXDOC-.diff
5. attach MPXDOC-.diff to the issue
6. wait for it to be applied

Remember to change  to the number given by JIRA.

But on a side note - I'm not exactly sure why you want to override these?

- Brett


> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, 5 May 2004 6:50 AM
> To: [EMAIL PROTECTED]
> Subject: xdoc with custom templates and/or navigation
>
>
> I have modified maven xdoc 1.6 to allow for the user to
> override the templates or navigation menu.  I use xdoc1.6
> that was included in the RC2
> release.  I am not sure where to post these changes.   I have
> include the
> two files changed to make this work.
> This give you the following new properties to control this:
>maven.xdoc.templates
>maven.xdoc.navigation
> (See attached file: plugin.jelly)(See attached file:
> plugin.properties) Regards, Garvin LeClaire Anthem Inc.
> Senior Technical Architect Technology Architecture and Infrastructure
> Tel: 513-336-3305
> CONFIDENTIALITY NOTICE: This e-mail message, including any
> attachments,
> is for the sole use of the intended recipient(s) and may
> contain confidential and privileged information or otherwise
> protected by law.  Any unauthorized review, use, disclosure
> or distribution is prohibited.  If you are not the intended
> recipient, please contact the sender by reply e-mail and
> destroy all copies of the original message.
>







CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, 
is for the sole use of the intended recipient(s) and may contain confidential
and privileged information or otherwise protected by law.  Any unauthorized
review, use, disclosure or distribution is prohibited.  If you are not the
intended recipient, please contact the sender by reply e-mail and destroy
all copies of the original message.

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

cvs commit: maven/xdocs/start release-notes.xml bootstrap.xml download.xml install.xml

[brett]

brett   2004/05/05 06:05:55

  Modified:.build-bootstrap.xml maven.xml project.properties
project.xml
   maven-jelly-tags/src/java/main/org/apache/maven/jelly/tags/maven
MavenTag.java MavenTagLibrary.java
PluginVarTag.java ReactorTag.java
   src/bin  maven
   src/conf defaults.properties
   src/java/org/apache/maven DependencyClasspathBuilder.java
MavenConstants.java MavenSession.java
MavenUtils.java
   src/java/org/apache/maven/cli App.java CLIManager.java
   src/java/org/apache/maven/jelly JellyBuildListener.java
JellyPropsHandler.java JellyUtils.java
MavenExpressionFactory.java MavenJellyContext.java
   src/java/org/apache/maven/jelly/tags/werkz
MavenAttainGoalTag.java MavenGoalTag.java
   src/java/org/apache/maven/plugin
GoalToJellyScriptHousingMapper.java
JellyScriptHousing.java PluginCacheManager.java
PluginDefinitionHandler.java PluginManager.java
PluginScriptParser.java
   src/java/org/apache/maven/project Build.java
Contributor.java PackageGroup.java Project.java
Repository.java
   src/java/org/apache/maven/util
CaseInsensitiveGlobPatternMapper.java
DVSLFormatter.java DVSLPathTool.java
EnhancedStringTokenizer.java Expand.java
HttpUtils.java MD5Sum.java MavenTool.java
ResourceBean.java StringTool.java
   src/java/org/apache/maven/verifier
ChecksumVerificationException.java
DependencyVerifier.java LocalSettingsVerifier.java
   src/test/java/org/apache/maven/plugin
PluginCacheManagerTest.java forehead.conf
   src/test/java/org/apache/maven/plugin/maven.home/plugins/jar/META-INF
MANIFEST.MF
   src/test/touchstone-build maven.xml project.xml
   src/test/touchstone-build/src/reactor-build/default
maven.xml
   src/test/touchstone-build/src/reactor-build/inheritence
maven.xml
   src/test/touchstone-build/src/reactor-build/inheritence/subproject
maven.xml
   
src/test/touchstone-build/src/reactor-build/inheritence/subproject/subproject2
maven.xml
   src/test/touchstone-build/src/reactor-build/resources
NOTES.txt
   src/test/touchstone-build/src/reactor-build/run_twice
NOTES.txt
   xdocschanges.xml development-process.xml navigation.xml
repository-upload.xml status.xml
   xdocs/misc articles.xml
   xdocs/reference dirlayout.xml project-descriptor.xml
user-guide.xml
   xdocs/start bootstrap.xml download.xml install.xml
  Added:   announcements 1.0-rc2.ann
   maven-jelly-tags .cvsignore project.properties project.xml
   maven-jelly-tags/src/java/main/org/apache/maven/jelly/tags/maven
GetTag.java InstallPluginTag.java SetTag.java
UninstallPluginTag.java
   maven-jelly-tags/xdocs changes.xml index.xml navigation.xml
   src/java/org/apache/maven/util Base64.java
   src/test/touchstone-build/src/reactor-build/default
project.properties
   xdocscvs-status.xml
   xdocs/start release-notes.xml
  Removed: src/java/org/apache/maven/jelly/tags BaseTagLibrary.java
BaseTagSupport.java package.html
   src/java/org/apache/maven/jelly/tags/maven AddPathTag.java
ConcatTag.java CopyResources.java
DependencyResolver.java
DependencyResolverInterface.java
GraphDependencyResolver.java InputTag.java
MakeAbsolutePathTag.java MakeRelativePathTag.java
MavenTag.java MavenTagLibrary.java ParamCheck.java
PluginVarTag.java PomTag.java PropertyTag.java
ReactorTag.java RootRelativePathTag.java
SnapshotSignature.java UserCheck.java
WerkzDependencyResolver.java package.html
   src/test/java/org/apache/maven/jelly/tags/maven
DependencyResolverTest.java
DependencyResolverTestData.java
RootRelat

RE: xdoc with custom templates and/or navigation

[Garvin . LeClaire]

Michal, you hit it right on.  If we do not give it a look and feel to match
our corporate standards our Technical Steering Commitee will see the
product as not being appropriate to use.
We all know this is technically wrong, but perception is reality when the
business people in the company are involved.
Yes I can use stylesheets for some but I also need the scripts to finish
the job.

Regards,

Garvin LeClaire
Anthem Inc.
Senior Technical Architect
Technology Architecture and Infrastructure
Tel: 513-336-3305




   

  Maczka Michal

  <[EMAIL PROTECTED]To:   "'Maven Developers List'" 
<[EMAIL PROTECTED]>  
  tf.ch>   cc: 

   Subject:  RE: xdoc with custom 
templates and/or navigation  
  05/05/2004 04:38 

  AM   

  Please respond to

  "Maven Developers

  List"

   

   







> -Original Message-
> From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, May 05, 2004 2:14 AM
> To: Maven Developers List
> Subject: RE: xdoc with custom templates and/or navigation
>
>
> On Tue, 2004-05-04 at 20:07, Brett Porter wrote:
> > The wiki has instructions on submitting patches.
> >
> > You need to do cvs diff -u against CVS HEAD for
> maven-plugins/xdoc, ie:
> >
> > 1. cvs checkout maven-plugins
> > 2. make changes in xdoc plugin there
> > 3. create issue in JIRA (MPXDOC- returned)
> > 4. do this:
> > cd maven-plugins
> > cvs diff -u xdoc >MPXDOC-.diff
> > 5. attach MPXDOC-.diff to the issue
> > 6. wait for it to be applied
> >
> > Remember to change  to the number given by JIRA.
> >
> > But on a side note - I'm not exactly sure why you want to
> override these?
>
> It's not one I'd like to see applied. Changing the structure of the
> output is not a good idea. If required I think it's just indicative of
> the stylesheet lacking certain elements. The application of the theme
> should be entirely possible via the stylesheets. If you want
> completely
> different output then do it with something else. This is not
> the sort of
> customization I want to see in any of the plugins.
>
> --
> jvz.
>

Jason!


It's not just a question of the "theme".
Some organization have already their own standards which define precisly
how
their intranet pages are looking.
Often thy have alredy hundreds of pages with spcific layout
which is completly different then this one which proposed by maven (for
example some of them are using html frames)
For them it might not only be attrative but simply necessry to have much
higher level of customization which will allow to generate what they want.

I understand that you intention is to have quite simillar (standard) sites
which are easy to browse. It's an appealing goal
but I think that most of the users will use the default theme anyway. But
if
somebody cannot do this or he does not want he should  be
free to go with his own solution.

BTW: in maven1 there are strange relations between site and xdoc plugins.
We
might imagine that somebody will be able to write his own replecment
for xdoc plugin and use it from site plugin.


Michal


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








CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, 
is for the sole use of the intended recipient(s) and may contain confidential
and privileged information or otherwise protected by law.  Any unauthorized
review, use, disclosure or distribution is prohibited.  If you are not the
intended recipient, please contact the sender by reply e-mail and destroy
all copies of the original message.

---

RE: xdoc with custom templates and/or navigation

[Garvin . LeClaire]

Is there a recommended way to modify the navigation menu?

Regards,

Garvin LeClaire
Anthem Inc.
Senior Technical Architect
Technology Architecture and Infrastructure
Tel: 513-336-3305




   

  Jason van Zyl

  <[EMAIL PROTECTED]To:   Maven Developers List 
<[EMAIL PROTECTED]>  
  g>   cc: 

   Subject:  RE: xdoc with custom 
templates and/or navigation  
  05/04/2004 08:14 

  PM   

  Please respond to

  "Maven Developers

  List"

   

   





On Tue, 2004-05-04 at 20:07, Brett Porter wrote:
> The wiki has instructions on submitting patches.
>
> You need to do cvs diff -u against CVS HEAD for maven-plugins/xdoc, ie:
>
> 1. cvs checkout maven-plugins
> 2. make changes in xdoc plugin there
> 3. create issue in JIRA (MPXDOC- returned)
> 4. do this:
> cd maven-plugins
> cvs diff -u xdoc >MPXDOC-.diff
> 5. attach MPXDOC-.diff to the issue
> 6. wait for it to be applied
>
> Remember to change  to the number given by JIRA.
>
> But on a side note - I'm not exactly sure why you want to override these?

It's not one I'd like to see applied. Changing the structure of the
output is not a good idea. If required I think it's just indicative of
the stylesheet lacking certain elements. The application of the theme
should be entirely possible via the stylesheets. If you want completely
different output then do it with something else. This is not the sort of
customization I want to see in any of the plugins.

--
jvz.

Jason van Zyl
[EMAIL PROTECTED]
http://maven.apache.org

happiness is like a butterfly: the more you chase it, the more it will
elude you, but if you turn your attention to other things, it will come
and sit softly on your shoulder ...

 -- Thoreau


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








CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, 
is for the sole use of the intended recipient(s) and may contain confidential
and privileged information or otherwise protected by law.  Any unauthorized
review, use, disclosure or distribution is prohibited.  If you are not the
intended recipient, please contact the sender by reply e-mail and destroy
all copies of the original message.

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

Re: groups syncing to ibiblio

[Mark R. Diggory]

I have a sense that someone is misinterpreting the purpose of rsyncing 
between Apache and Ibiblio. We setup the rsync based on the the 
following criteria/decisions:

1.) Organizational Management: Apache has to be the canonical release 
point for all Apache content. This means that if there is an Apache 
package in ibiblio that is not placed there via the rsync process, then 
we should discuss means of getting it back over on Apache. No Apache 
project now actually requires a ibiblio account to get its content onto 
ibiblio, they already have apache accounts and can easily do it there. 
No rouge developers should put Apache content into the ibiblio 
directory, they should consult with Apache to get it added to our 
repository which is then rsynced.

2.) Scalability and Workload: Having either "everyone" with a project 
have an account at ibiblio or send email/jira requests in that have to 
be "manually" processed is not scalable. The goal behind the Apache 
rsync is to alleviate also this problem. Apache has a fairly high trust 
relationship between its developers and with mirroring/rsync already 
available throughout the world, this is just an extension of that trust 
relationship.

I think its a great idea to have other organizations who wish to rsync 
use the script. But this should be a decision within those groups, if 
you are a member of that groups and you object, you should take it up 
with that group. The rsync is a management tool to make the repository 
managers jobs easier.

The goal here is to build a stable and scalable repository of trusted 
content, not to have a "anarchy" diskspace where you can't trust anyones 
content. To do this requires stronger "institutional" management of the 
larger groups like Apache, Codehaus etc. and the proper signing (both 
md5 and pgp) of artifacts...

With this is mind, Jason, how close are we to having "hierarchical" 
organization/group directories? My point is that it would be far easier 
for us to control any overlap in projects if the organizations were 
isolated into separate directories.

for instance

www.ibiblio.org/maven/apache/
www.ibiblio.org/maven/codehaus/
also, is it possible to get virtual host names out of Ibiblio, ie

maven.ibiblio.org/apache/
maven.ibiblio.org/codehaus/
Maybe this is something we can really push for version two, before there 
are too many dependent projects?

-Mark

Vincent Massol wrote:

-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: 04 May 2004 18:10
To: Maven Developers List
Subject: RE: groups syncing to ibiblio
On Tue, 2004-05-04 at 11:48, Vincent Massol wrote:


Why should aspectwerkz artifacts that you place in ibiblio take
precedence over what the AspectWerkz developers actually have
moved to

ibiblio?
Whatever is newer should take precedence.
Not if the difference is between the project and third party. We're
only

starting to have the capability to allow projects govern their own
artifact deployment to Ibiblio. In the cases where projects have
direct

control we no long have any say. What they deploy rules.


See below


Anyway, here are my 2 reasons:

1/ Simply because otherwise I won't be able to help on this subject.
A

pity I think as I could have helped as I was currently doing (and
I've

done my share of ibiblio uploads).
You don't need to for projects that have direct access, but all the
other requests you can still certainly help.


See below


2/ Because if a project jar is released by the project under an open
source license I don't see why it matters to get the authorization
from

that project to put it up on ibiblio.
You don't legally, it's a matter of courtesy. If the project has
access

to ibiblio they should dictate what goes into ibiblio and this will be
a

policy I would like to enact. I think it only makes sense that in
cases

where projects have direct access (and this will be case always when
automated uploads work) to control what artifacts go into ibiblio.


I believe it's up to them. Why do you want to decide for them? If they
say that they want to control it, then it's fine of course and we will
let them do it. However, if they do accept our help then I don't see why
we couldn't help. And then I don't see what's the problem updating these
files from ibiblio directly or through their repo. Provided of course
(which is what I was asking) that the synchronization is bidirectional.
If that's not possible then all this discussion is moot. I don't know
rsync enough to know what's possible or not.

Ideally I agree it would be nice,
but when you're in a hurry doing something, it's simply a pain being
delayed.
Sure, but with the sync from apache and codehaus the most you have to
wait is 4 hours and that interval could shortened if deemed necessary.

I have no idea where this repository is, whether I have the karma,
how

to do it, etc. I don't have the will to check this out for now.
Well, it's board policy and messages have been posted. You cannot be
deploying direc

cvs commit: maven/src/man maven.1

[trygvis]

trygvis 2004/05/05 05:25:58

  Modified:src/man  maven.1
  Log:
  Updating the man page:
   o Adding new authors.
   o Adding the new command line options.
   o Some reformatting of the options to look more 'normal'.
  
  Revision  ChangesPath
  1.2   +28 -21maven/src/man/maven.1
  
  Index: maven.1
  ===
  RCS file: /home/cvs/maven/src/man/maven.1,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- maven.1   26 Mar 2003 10:40:58 -  1.1
  +++ maven.1   5 May 2004 12:25:57 -   1.2
  @@ -1,11 +1,12 @@
   .\" Process this file with
   .\" groff -man -Tascii foo.1
   .\"
  -.TH MAVEN 1 "MARCH 2003" Linux "User Manuals"
  +.TH MAVEN 1 "MAY 2004" Linux "User Manuals"
   .SH NAME
   maven \- builds a project
   .SH SYNOPSIS
  -\fB maven\fR [\fIoptions\fR] \fIgoal\fR ...
  +\fB maven\fR [\fIoptions\fR] [\fIgoal\fR [\fIgoal2\fR [\fIgoal3\fR] ...]]
  +
   .SH DESCRIPTION
   .B Maven
   is a Java project management and project comprehension tool. Maven is
  @@ -27,47 +28,50 @@
   .SH OPTIONS
   Options must be given before the list of goals to execute.
   .TP
  -\fB\-\-debug\fR (\fB\-X\fR)
  +\fB\-X\fR, \fB\-\-debug\fR
   Produce execution debug output
   .TP
  -\fB\-\-emacs\fR (\fB\-E\fR)
  -Produce logging information without adornments.
  -.TP
  -\fB\-\-define\fR arg (\fB-D\fRarg)
  +\fB\-D\fR, \fB\-\-define\fR \fIarg\fR
   Define a system property.
   arg must be in the form: 
   .br
  -\fBmaven.property.name\fI=\fRvalue
  -.TP
  -\fB\-\-nobanner\fR (\fB\-b)
  -Suppress the logo banner.
  +maven.property.name=value
   .TP
  -\fB\-\-dir\fR (\fB\-d\fR) arg
  +\fB\-d\fR, \fB\-\-dir\fR \fIarg\fR
   Set the effective working directory.
   .TP
  -\fB\-\-exception\fR (\fB\-e\fR)
  +\fB\-E\fR, \fB\-\-emacs\fR
  +Produce logging information without adornments.
  +.TP
  +\fB\-e\fR, \fB\-\-exception\fR
   Produce exception stack traces.
   .TP
  -\fB\-\-find\fR (\fB-f\fR) arg
  +\fB\-f\fR, \fB\-\-find\fR \fIarg\fR
   Set the project file and effective working directory by finding the project.
   file.
   .TP
  -\fB\-\-goals\fR (\fB\-g\fR)
  +\fB\-g\fR, \fB\-\-goals\fR
   Display available goals.
   .TP
  -\fB\-\-help\fR (\fB\-h\fR)
  +\fB\-h\fR, \fB\-\-help\fR
   Display help information.
   .TP
  -\fB\-\-info\fR (\fB\-i\fR)
  +\fB\-i\fR, \fB\-\-info\fR
   Display system information.
   .TP
  -\fB\-\-offline\fR (\fB\-o\fR)
  +\fB\-b\fR, \fB\-\-nobanner\fR
  +Suppress the logo banner.
  +.TP
  +\fB\-o\fR, \fB\-\-offline\fR
   Build is happening offline.
   .TP
  -\fB\-\-pom\fR (\fB\-p\fR) arg
  +\fB\-p\fR, \fB\-\-pom\fR \fIarg\fR
   Set the project file.
   .TP
  -\fB\-\-version\fR (\fB\-v\fR)
  +\fB\-q\fR, \fB\-\-quitet\fR \fIarg\fR
  +Reduce execution output.
  +.TP
  +\fB\-v\fR, \fB\-\-version\fR
   Display the version of \fBmaven\fR we are using.
   .SH FILES
   .I ./build.properties
  @@ -135,3 +139,6 @@
   Ben Walding <[EMAIL PROTECTED]>
   .SH CVS HEADER
   $Id$
  +.SH AUTHOR
  +This man page was originally written Stephane Mor <[EMAIL PROTECTED]>
  +and updated by Trygve Laugstoel <[EMAIL PROTECTED]>
  
  
  

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

RE: xdoc with custom templates and/or navigation

[Jason van Zyl]

On Wed, 2004-05-05 at 04:38, Maczka Michal wrote:

> Jason!
> 
> 
> It's not just a question of the "theme".
> Some organization have already their own standards which define precisly how
> their intranet pages are looking.
> Often thy have alredy hundreds of pages with spcific layout
> which is completly different then this one which proposed by maven (for
> example some of them are using html frames) 
> For them it might not only be attrative but simply necessry to have much
> higher level of customization which will allow to generate what they want.

That's fine, they can use tools like StaticMesh or SiteMesh alter
anything they like, or integrate whatever portions of the maven
generated sites they like.

> I understand that you intention is to have quite simillar (standard) sites
> which are easy to browse. It's an appealing goal
> but I think that most of the users will use the default theme anyway. But if
> somebody cannot do this or he does not want he should  be
> free to go with his own solution. 

They can, it's just not something I want baked in. I also say this
because the new xdoc plugin is blindingly fast because I'm directly
writing out the xhtml from xml by passing the use of any other tools
which is why it is so fast and so small. This is I will not sacrifice
for users every whim for customization. This level of customization is
entirely, and easily possibly with the StaticMesh/SiteMesh tools.

> BTW: in maven1 there are strange relations between site and xdoc plugins. We
> might imagine that somebody will be able to write his own replecment
> for xdoc plugin and use it from site plugin.

Yes, but ultimately the must conform to the xdoc style of document or
they basically get no benefit from any of the plugins that produce the
xdoc style. At any rate, these cases will be few and far between and for
those cases tools exist to munge the generated xdoc or style xhtml in
anyway shape or form.

-- 
jvz.

Jason van Zyl
[EMAIL PROTECTED]
http://maven.apache.org

happiness is like a butterfly: the more you chase it, the more it will
elude you, but if you turn your attention to other things, it will come
and sit softly on your shoulder ...

 -- Thoreau 


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

[jira] Created: (MPJXR-12) Create a named anchor for each symbol like Javadoc does

[jira]

Message:

  A new issue has been created in JIRA.

-
View the issue:
  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPJXR-12

Here is an overview of the issue:
-
Key: MPJXR-12
Summary: Create a named anchor for each symbol like Javadoc does
   Type: Improvement

 Status: Open
   Priority: Minor

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

Project: maven-jxr-plugin

   Assignee: Jason van Zyl
   Reporter: Laurent Caillette

Created: Wed, 5 May 2004 8:10 AM
Updated: Wed, 5 May 2004 8:10 AM

Description:
I want to reference source code from XDoc. By now I'm writing a link like this:
method here

The problem is, my link can lead to a wrong place just after a few cosmetic changes in 
source code. Of course, automatic link check will not guess the link went wrong.

It would be nice to generate named anchors in XRef the same way Javadoc does, 
supporting a link like this from XDoc:
method here

Another way to achieve the same result would be to parse Java comments to find a 
special expression to be transformed in a named anchor, but the Javadoc way seems more 
straightforward.



-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


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

cvs commit: maven-plugins/plugin-parent project.xml

[brett]

brett   2004/05/05 05:04:28

  Modified:.project.xml project.properties
   plugin-parent project.xml
  Log:
  doco updates
  
  Revision  ChangesPath
  1.21  +10 -0 maven-plugins/project.xml
  
  Index: project.xml
  ===
  RCS file: /home/cvs/maven-plugins/project.xml,v
  retrieving revision 1.20
  retrieving revision 1.21
  diff -u -r1.20 -r1.21
  --- project.xml   5 May 2004 07:34:37 -   1.20
  +++ project.xml   5 May 2004 12:04:28 -   1.21
  @@ -118,6 +118,16 @@
   Release Manager
 
   
  +
  +  Brett Porter
  +  brett
  +  [EMAIL PROTECTED]
  +  f2 network
  +  
  +Developer
  +  
  +  +10
  +
 
   
 
  
  
  
  1.14  +3 -0  maven-plugins/project.properties
  
  Index: project.properties
  ===
  RCS file: /home/cvs/maven-plugins/project.properties,v
  retrieving revision 1.13
  retrieving revision 1.14
  diff -u -r1.13 -r1.14
  --- project.properties5 May 2004 07:34:37 -   1.13
  +++ project.properties5 May 2004 12:04:28 -   1.14
  @@ -36,3 +36,6 @@
   maven.multiproject.overviewPage.link=plugins
   maven.multiproject.overviewPage.text=The following Maven plugins are available:
   maven.multiproject.excludes=plugin-parent/project.xml
  +
  +maven.xdoc.date = left
  +maven.xdoc.date.format = dd   HH:mm z
  
  
  
  1.3   +10 -0 maven-plugins/plugin-parent/project.xml
  
  Index: project.xml
  ===
  RCS file: /home/cvs/maven-plugins/plugin-parent/project.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- project.xml   2 May 2004 14:50:02 -   1.2
  +++ project.xml   5 May 2004 12:04:28 -   1.3
  @@ -119,6 +119,16 @@
   Release Manager
 
   
  +
  +  Brett Porter
  +  brett
  +  [EMAIL PROTECTED]
  +  f2 network
  +  
  +Developer
  +  
  +  +10
  +
 
   
 
  
  
  

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

Re: [jira] Commented: (MPECLIPSE-25) Add the capability of specifying more builders

[Felipe Leme]

Hi all,

Regardless of this patche fixing the bug or not, I think we could go a 
step further on the Eclipse project/nature/builder support. Let me 
explain better.

For the case of 'less intrusive' Eclipse plugins (like Checkstyle), I 
think the patch is fine. But that is not enough for plugins that takes 
more control of your eclipse workspace - there are some plugins, for 
instance, that creates some XML files or even copy other jars in your 
project. More than that, you might want to support multiple plugins in 
your project, according to each developer preference (or budget 
limitation).  Take for instance web/J2EE development. There are many 
plugins available for the task, being MyEclipseIDE and Lomboz the most 
popular ones. It would be nice if the same maven-powered project could 
be used by any of these plugins. So, in those cases, we would have 
specific goals for each plugin. Something like:

maven eclipse:eclipse -> default java project
maven eclispe:myeclipseide
maven eclipse:lomboz
and so on
We would still apply dion's patch so we can manually define our project 
builders, but when we call these new goals, the goal itself would know 
what builders/nature it must use.

Another thing that would be useful is to define the web structure of 
your application (i.e., where the files are, which JARs should be in the 
libetc...) in the POM, so these plugins could create the right structure 
in place (for instance, copying the jars from $MAVEN_HOME to 
web/WEB-INF/lib). But this is not specfic to the Eclipse plug-in, it 
should be something 'maven-widely' (maybe the current POM model already 
supports it - I'm still a semi-newbie maven user, so sorry if it already 
does and I didn't know :-).

Finally, once we discuss this issue and decide if it is usefull or not 
(i.e., if a new patch would be accepted/committed in), I could open a 
new bug describing it and even work on the patches (in fact, I should 
have done that already, but been too busy to - right now we are just 
using the default eclipse:eclise goal and then manually using 
MyEclipseIDE to add a web-module on the project).

Regards,

Felipe

[EMAIL PROTECTED] wrote:

The following comment has been added to this issue:

Author: dion gillard
   Created: Tue, 4 May 2004 9:04 PM
  Body:
This patch looks ok to me. It would be nice if we had a test case for it, but I can 
apply and test if everyone is ok with it
 

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

[jira] Updated: (MAVEN-1260) please upload xmlstubs-1.0.1 on ibiblio

[jira]

The following issue has been updated:

Updater: nicolas de loof (mailto:[EMAIL PROTECTED])
   Date: Wed, 5 May 2004 7:31 AM
Changes:
 Attachment changed to ibiblio.txt
-
For a full history of the issue, see:

  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1260&page=history

-
View the issue:
  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1260

Here is an overview of the issue:
-
Key: MAVEN-1260
Summary: please  upload xmlstubs-1.0.1 on ibiblio
   Type: Wish

 Status: Unassigned
   Priority: Major

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

Project: maven

   Assignee: 
   Reporter: nicolas de loof

Created: Tue, 4 May 2004 5:39 AM
Updated: Wed, 5 May 2004 7:31 AM

Description:
please  upload xmlstubs-1.0.1 on ibiblio

azote
xmlstubs
1.0.1

licensed under apache http://www.apache.org/licenses/LICENSE-2.0


-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


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

[jira] Created: (MAVEN-1268) keep release profile of plugins bundled

[jira]

Message:

  A new issue has been created in JIRA.

-
View the issue:
  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1268

Here is an overview of the issue:
-
Key: MAVEN-1268
Summary: keep release profile of plugins bundled
   Type: Task

 Status: Unassigned
   Priority: Major

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

Project: maven
 Components: 
 installer
   Fix Fors:
 1.0

   Assignee: 
   Reporter: Brett Porter

Created: Wed, 5 May 2004 7:31 AM
Updated: Wed, 5 May 2004 7:31 AM

Description:
split code that sucks in the plugin list to distribute into a goal that generates a 
profile that can be stored and tagged in CVS. installer should use the profile to 
generate the distribution so it is reproducable.


-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


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

[jira] Created: (MAVEN-1267) create source distribution for Maven 1.0 as part of installer process

[jira]

Message:

  A new issue has been created in JIRA.

-
View the issue:
  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1267

Here is an overview of the issue:
-
Key: MAVEN-1267
Summary: create source distribution for Maven 1.0 as part of installer process
   Type: Task

 Status: Open
   Priority: Major

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

Project: maven
 Components: 
 installer
   Fix Fors:
 1.0

   Assignee: Brett Porter
   Reporter: Brett Porter

Created: Wed, 5 May 2004 7:29 AM
Updated: Wed, 5 May 2004 7:29 AM

Description:
currently build several binaries, but no source distribution


-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


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

cvs commit: maven/maven-jelly-tags project.properties

[brett]

brett   2004/05/05 04:04:36

  Added:   maven-jelly-tags/xdocs Tag: MAVEN-1_0-BRANCH navigation.xml
   maven-jelly-tags Tag: MAVEN-1_0-BRANCH project.properties
  Log:
  update jelly tag site
  
  Revision  ChangesPath
  No   revision
  No   revision
  1.1.2.1   +35 -0 maven/maven-jelly-tags/xdocs/Attic/navigation.xml
  
  
  
  
  No   revision
  No   revision
  1.1.2.1   +7 -0  maven/maven-jelly-tags/Attic/project.properties
  
  
  
  

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

cvs commit: maven/src/test/touchstone-build maven.xml

[brett]

brett   2004/05/05 04:04:10

  Modified:src/test/touchstone-build Tag: MAVEN-1_0-BRANCH maven.xml
  Log:
  test for getDependencyPath
  
  Revision  ChangesPath
  No   revision
  No   revision
  1.43.4.14 +15 -0 maven/src/test/touchstone-build/maven.xml
  
  Index: maven.xml
  ===
  RCS file: /home/cvs/maven/src/test/touchstone-build/maven.xml,v
  retrieving revision 1.43.4.13
  retrieving revision 1.43.4.14
  diff -u -r1.43.4.13 -r1.43.4.14
  --- maven.xml 24 Apr 2004 23:11:23 -  1.43.4.13
  +++ maven.xml 5 May 2004 11:04:10 -   1.43.4.14
  @@ -213,6 +213,7 @@
   
   
   
  +
   
   

cvs commit: maven-plugins/xdocs index.xml

[brett]

brett   2004/05/05 04:02:54

  Modified:xdocsindex.xml
  Log:
  add mevenide link
  
  Revision  ChangesPath
  1.2   +10 -2 maven-plugins/xdocs/index.xml
  
  Index: index.xml
  ===
  RCS file: /home/cvs/maven-plugins/xdocs/index.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- index.xml 5 May 2004 07:36:03 -   1.1
  +++ index.xml 5 May 2004 11:02:54 -   1.2
  @@ -83,12 +83,20 @@
 
   
 
  +  
  +
  +   
  + http://mevenide.codehaus.org/maven-nbm-plugin";>Maven NBM 
plugin
  +Plugin for creating Netbeans modules (both jars and NBMs) and 
autoupdate sites.
  +   
  + 
  +  
   
   
 
   
  -  http://mevenide.sourceforge.net/";>Mevenide
  -  Mevenide (Maven IDE Integration) aims at integrating Maven into 
standard IDEs. Currently only Eclipse is targeted.
  +  http://mevenide.codehaus.org/";>Mevenide
  +  Mevenide (Maven IDE Integration) aims at integrating Maven into 
standard IDEs. Currently Eclipse and Netbeans are targeted.
   
 
   
  
  
  

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

cvs commit: maven/src/java/org/apache/maven DependencyClasspathBuilder.java

[brett]

brett   2004/05/05 04:02:44

  Modified:src/java/org/apache/maven Tag: MAVEN-1_0-BRANCH
DependencyClasspathBuilder.java
  Log:
  PR: MAVEN-1265
  dependency path setting for non-classpath dependencies
  
  Revision  ChangesPath
  No   revision
  No   revision
  1.13.4.6  +2 -2  maven/src/java/org/apache/maven/DependencyClasspathBuilder.java
  
  Index: DependencyClasspathBuilder.java
  ===
  RCS file: /home/cvs/maven/src/java/org/apache/maven/DependencyClasspathBuilder.java,v
  retrieving revision 1.13.4.5
  retrieving revision 1.13.4.6
  diff -u -r1.13.4.5 -r1.13.4.6
  --- DependencyClasspathBuilder.java   28 Mar 2004 21:27:26 -  1.13.4.5
  +++ DependencyClasspathBuilder.java   5 May 2004 11:02:44 -   1.13.4.6
  @@ -61,8 +61,8 @@
   if ( d.isAddedToClasspath() )
   {
   classpath.append( artifact.getPath() ).append( cps );
  -project.setDependencyPath( d.getId(), artifact.getPath() );
   }
  +project.setDependencyPath( d.getId(), artifact.getPath() );
   }
   
   return classpath.toString();
  
  
  

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

cvs commit: maven/xdocs changes.xml

[brett]

brett   2004/05/05 04:01:05

  Modified:maven-jelly-tags/xdocs Tag: MAVEN-1_0-BRANCH changes.xml
   xdocsTag: MAVEN-1_0-BRANCH changes.xml
  Log:
  change log
  
  Revision  ChangesPath
  No   revision
  No   revision
  1.1.2.2   +2 -0  maven/maven-jelly-tags/xdocs/Attic/changes.xml
  
  Index: changes.xml
  ===
  RCS file: /home/cvs/maven/maven-jelly-tags/xdocs/Attic/changes.xml,v
  retrieving revision 1.1.2.1
  retrieving revision 1.1.2.2
  diff -u -r1.1.2.1 -r1.1.2.2
  --- changes.xml   28 Apr 2004 03:28:57 -  1.1.2.1
  +++ changes.xml   5 May 2004 11:01:04 -   1.1.2.2
  @@ -25,6 +25,8 @@
 
 
   
  +  Added new SetTag tag to set 
plugin properties
  +  Added new GetTag tag that 
replaces the now deprecated PluginVar tag
 Install and uninstall 
plugin tags for managing plugins on the fly.
   
 
  
  
  
  No   revision
  No   revision
  1.14.4.15 +1 -2  maven/xdocs/changes.xml
  
  Index: changes.xml
  ===
  RCS file: /home/cvs/maven/xdocs/changes.xml,v
  retrieving revision 1.14.4.14
  retrieving revision 1.14.4.15
  diff -u -r1.14.4.14 -r1.14.4.15
  --- changes.xml   29 Apr 2004 21:36:51 -  1.14.4.14
  +++ changes.xml   5 May 2004 11:01:04 -   1.14.4.15
  @@ -25,8 +25,7 @@
 
 
   
  -  Added new SetTag tag to set 
plugin properties
  -  Added new GetTag tag that 
replaces the now deprecated PluginVar tag
  +  Setup dependency path for 
non-classpath dependencies
 Add 
a Base64 implementation to replace the sun.* internal version.
 Remove tools.jar from 
startup classpath so it will run on non-Sun JVMs such as Kaffe.
 Allow plugin installation 
and uninstallation from the plugin manager and the cache so that it can be done on the 
fly.
  
  
  

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

cvs commit: maven-plugins/xdoc project.xml

[brett]

brett   2004/05/05 04:00:59

  Modified:artifact project.xml
   changelog project.xml
   linkcheck project.xml
   multiproject project.xml
   pom  project.xml
   release  project.xml
   xdoc project.xml
  Log:
  update maven JAR
  
  Revision  ChangesPath
  1.20  +1 -1  maven-plugins/artifact/project.xml
  
  Index: project.xml
  ===
  RCS file: /home/cvs/maven-plugins/artifact/project.xml,v
  retrieving revision 1.19
  retrieving revision 1.20
  diff -u -r1.19 -r1.20
  --- project.xml   2 May 2004 13:29:39 -   1.19
  +++ project.xml   5 May 2004 11:00:59 -   1.20
  @@ -51,7 +51,7 @@
   
 maven
 maven
  -  1.0-beta-10
  +  1.0-rc2
 jar
   
   
  
  
  
  1.37  +1 -1  maven-plugins/changelog/project.xml
  
  Index: project.xml
  ===
  RCS file: /home/cvs/maven-plugins/changelog/project.xml,v
  retrieving revision 1.36
  retrieving revision 1.37
  diff -u -r1.36 -r1.37
  --- project.xml   2 May 2004 13:34:11 -   1.36
  +++ project.xml   5 May 2004 11:00:59 -   1.37
  @@ -138,7 +138,7 @@
   
 maven
 maven
  -  1.0-beta-10
  +  1.0-rc2
   
   
   
  
  
  
  1.44  +1 -1  maven-plugins/linkcheck/project.xml
  
  Index: project.xml
  ===
  RCS file: /home/cvs/maven-plugins/linkcheck/project.xml,v
  retrieving revision 1.43
  retrieving revision 1.44
  diff -u -r1.43 -r1.44
  --- project.xml   2 May 2004 14:16:24 -   1.43
  +++ project.xml   5 May 2004 11:00:59 -   1.44
  @@ -130,7 +130,7 @@
   
 maven
 maven
  -  1.0-beta-10
  +  1.0-rc2
   
   
 js-1.5R4-RC3.jar
  
  
  
  1.25  +1 -1  maven-plugins/multiproject/project.xml
  
  Index: project.xml
  ===
  RCS file: /home/cvs/maven-plugins/multiproject/project.xml,v
  retrieving revision 1.24
  retrieving revision 1.25
  diff -u -r1.24 -r1.25
  --- project.xml   2 May 2004 14:27:09 -   1.24
  +++ project.xml   5 May 2004 11:00:59 -   1.25
  @@ -103,7 +103,7 @@
 maven
 maven
 jar
  -  1.0-beta-10
  +  1.0-rc2
   
 
   
  
  
  
  1.38  +1 -1  maven-plugins/pom/project.xml
  
  Index: project.xml
  ===
  RCS file: /home/cvs/maven-plugins/pom/project.xml,v
  retrieving revision 1.37
  retrieving revision 1.38
  diff -u -r1.37 -r1.38
  --- project.xml   2 May 2004 14:16:25 -   1.37
  +++ project.xml   5 May 2004 11:00:59 -   1.38
  @@ -86,7 +86,7 @@
 maven.jar
 maven
 maven
  -  1.0-beta-10
  +  1.0-rc2
   
   
 isorelax
  
  
  
  1.30  +1 -1  maven-plugins/release/project.xml
  
  Index: project.xml
  ===
  RCS file: /home/cvs/maven-plugins/release/project.xml,v
  retrieving revision 1.29
  retrieving revision 1.30
  diff -u -r1.29 -r1.30
  --- project.xml   2 May 2004 14:16:25 -   1.29
  +++ project.xml   5 May 2004 11:00:59 -   1.30
  @@ -51,7 +51,7 @@
 maven.jar
 maven
 maven
  -  1.0-beta-10
  +  1.0-rc2
   
   
 commons-io
  
  
  
  1.47  +1 -1  maven-plugins/xdoc/project.xml
  
  Index: project.xml
  ===
  RCS file: /home/cvs/maven-plugins/xdoc/project.xml,v
  retrieving revision 1.46
  retrieving revision 1.47
  diff -u -r1.46 -r1.47
  --- project.xml   2 May 2004 14:27:09 -   1.46
  +++ project.xml   5 May 2004 11:00:59 -   1.47
  @@ -130,7 +130,7 @@
   
 maven
 maven
  -  1.0-beta-10
  +  1.0-rc2
   
   
 velocity
  
  
  

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

[jira] Closed: (MAVEN-1265) getDependencyPath fails for nonstandard types

[jira]

Message:

   The following issue has been closed.

   Resolver: Brett Porter
   Date: Wed, 5 May 2004 6:50 AM

fixed for non standard types. No need to add :tld etc to the end of the id (current 
legacy ID parser doesn't handle that consistently anyway).


-
View the issue:
  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1265

Here is an overview of the issue:
-
Key: MAVEN-1265
Summary: getDependencyPath fails for nonstandard types
   Type: Bug

 Status: Closed
   Priority: Major
 Resolution: FIXED

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

Project: maven
 Components: 
 core
   Fix Fors:
 1.0-rc3
   Versions:
 1.0-rc2

   Assignee: Brett Porter
   Reporter: Matt Johnson

Created: Tue, 4 May 2004 11:45 PM
Updated: Wed, 5 May 2004 6:50 AM
Environment: WinXP, cygwin

Description:
When attempting to retrieve dependency path information, 
${pom.getDependencyPath('my.dependency.id')} is empty for dependencies which have a 
nonstandard .

Workaround is to iterate over ${pom.artifacts} and compare dependency id's to the one 
you're after.


-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


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

[jira] Reopened: (MAVEN-1216) NoClassDefFoundError for org/jaxen/JaxenException and org/saxpath/SAXPathException

[jira]

Message:

   The following issue has been reopened.

-
View the issue:
  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1216

Here is an overview of the issue:
-
Key: MAVEN-1216
Summary: NoClassDefFoundError for org/jaxen/JaxenException  and 
org/saxpath/SAXPathException
   Type: Bug

 Status: Reopened
   Priority: Major

 Original Estimate: 1 hour
 Time Spent: Unknown
  Remaining: 1 hour

Project: maven
 Components: 
 jelly/ant integration
   Fix Fors:
 1.0-rc3
   Versions:
 1.0-rc2

   Assignee: Brett Porter
   Reporter: Vladimir Kralik

Created: Thu, 1 Apr 2004 9:51 AM
Updated: Wed, 5 May 2004 6:44 AM
Environment: maven-1.0-rc2
jdk 1.4.2_03
M$ Windows 2000 SP 4
cygwin

Description:
When I try install my own plugin ( by using "maven plugin:install" ),then I get :
<>
Caused by: java.lang.NoClassDefFoundError: org/jaxen/JaxenException
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:141)
at 
org.apache.commons.jelly.tags.xml.XMLTagLibrary.class$(XMLTagLibrary.java:82)
<>

after "cp jaxen-core-1.0-FCS.jar $MAVEN_HOME/lib" :

<>
Caused by: java.lang.NoClassDefFoundError: org/saxpath/SAXPathException
<>>
at 
org.apache.commons.jelly.tags.xml.XMLTagLibrary.class$(XMLTagLibrary.java:82)
<>

after "cp saxpath-1.0-FCS.jar $MAVEN_HOME/lib"

it works fine.

jaxen and saxpath are not listed as dependecies in my plugin.
I use very simple Hello World plugin ( see below )

I thing that problem is in jelly-integration, because jelly 
(org.apache.commons.jelly.tags.xml.ForEachTag) requires org.jaxen.JaxenException and 
dom4j (org.dom4j.xpath.XPathPattern) requieres org.saxpath.SAXPathException.

===
project.xml
===


  3
  maven-hello-plugin
  Maven Hello World Plug-in
  1.0.0-SNAPSHOT
  
  

  
${basedir}

  plugin.jelly
  plugin.properties
  project.xml

  

  

===
plugin.jelly
===



Hello, ${maven.hello.world}


===
plugin.properties
===
maven.hello.world=World


-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


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

[jira] Updated: (MAVEN-1216) NoClassDefFoundError for org/jaxen/JaxenException and org/saxpath/SAXPathException

[jira]

The following issue has been updated:

Updater: Brett Porter (mailto:[EMAIL PROTECTED])
   Date: Wed, 5 May 2004 6:45 AM
Changes:
 Fix Version changed to 1.0-rc3
-
For a full history of the issue, see:

  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1216&page=history

-
View the issue:
  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1216

Here is an overview of the issue:
-
Key: MAVEN-1216
Summary: NoClassDefFoundError for org/jaxen/JaxenException  and 
org/saxpath/SAXPathException
   Type: Bug

 Status: Reopened
   Priority: Major

 Original Estimate: 1 hour
 Time Spent: Unknown
  Remaining: 1 hour

Project: maven
 Components: 
 jelly/ant integration
   Fix Fors:
 1.0-rc3
   Versions:
 1.0-rc2

   Assignee: Brett Porter
   Reporter: Vladimir Kralik

Created: Thu, 1 Apr 2004 9:51 AM
Updated: Wed, 5 May 2004 6:45 AM
Environment: maven-1.0-rc2
jdk 1.4.2_03
M$ Windows 2000 SP 4
cygwin

Description:
When I try install my own plugin ( by using "maven plugin:install" ),then I get :
<>
Caused by: java.lang.NoClassDefFoundError: org/jaxen/JaxenException
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:141)
at 
org.apache.commons.jelly.tags.xml.XMLTagLibrary.class$(XMLTagLibrary.java:82)
<>

after "cp jaxen-core-1.0-FCS.jar $MAVEN_HOME/lib" :

<>
Caused by: java.lang.NoClassDefFoundError: org/saxpath/SAXPathException
<>>
at 
org.apache.commons.jelly.tags.xml.XMLTagLibrary.class$(XMLTagLibrary.java:82)
<>

after "cp saxpath-1.0-FCS.jar $MAVEN_HOME/lib"

it works fine.

jaxen and saxpath are not listed as dependecies in my plugin.
I use very simple Hello World plugin ( see below )

I thing that problem is in jelly-integration, because jelly 
(org.apache.commons.jelly.tags.xml.ForEachTag) requires org.jaxen.JaxenException and 
dom4j (org.dom4j.xpath.XPathPattern) requieres org.saxpath.SAXPathException.

===
project.xml
===


  3
  maven-hello-plugin
  Maven Hello World Plug-in
  1.0.0-SNAPSHOT
  
  

  
${basedir}

  plugin.jelly
  plugin.properties
  project.xml

  

  

===
plugin.jelly
===



Hello, ${maven.hello.world}


===
plugin.properties
===
maven.hello.world=World


-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


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

[jira] Commented: (MPCHANGELOG-38) changelog does not work with cvsnt

[jira]

The following comment has been added to this issue:

 Author: Archimedes Trajano
Created: Wed, 5 May 2004 5:26 AM
   Body:
Just checked http://javacvs.netbeans.org/issues/show_bug.cgi?id=39662 it says its just 
an informational message, but it does not explain why I do not get any results back 
from the CVS server for changelog.

BTW I run the plugin as 

maven maven-changelog-plugin:report

as the documented goals do not work.

C:\Project>maven changelog
 __  __
|  \/  |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \  ~ intelligent projects ~
|_|  |_\__,_|\_/\___|_||_|  v. 1.0-rc3-SNAPSHOT

com.werken.werkz.NoSuchGoalException: No goal [changelog]

C:\Projects>maven changelog:generate
 __  __
|  \/  |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \  ~ intelligent projects ~
|_|  |_\__,_|\_/\___|_||_|  v. 1.0-rc3-SNAPSHOT

com.werken.werkz.NoSuchGoalException: No goal [changelog:generate]
-
View this comment:
  
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPCHANGELOG-38&page=comments#action_19380

-
View the issue:
  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPCHANGELOG-38

Here is an overview of the issue:
-
Key: MPCHANGELOG-38
Summary: changelog does not work with cvsnt
   Type: Bug

 Status: Unassigned
   Priority: Major

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

Project: maven-changelog-plugin
   Versions:
 1.5

   Assignee: 
   Reporter: Archimedes Trajano

Created: Tue, 4 May 2004 1:35 PM
Updated: Wed, 5 May 2004 5:26 AM
Environment: CVSNT 2.0.26

Description:
C:\Projects\pensions>maven maven-changelog-plugin:report
 __  __
|  \/  |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \  ~ intelligent projects ~
|_|  |_\__,_|\_/\___|_||_|  v. 1.0-rc3-SNAPSHOT

build:start:

maven-changelog-plugin:report:
[echo] Generating the changelog report
Server is not supporting gzip-file-contents request
ChangeLog found: 0 entries
BUILD SUCCESSFUL
Total time: 5 seconds
Finished at: Tue May 04 19:27:12 CEST 2004



-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


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

RE: xdoc with custom templates and/or navigation

[Maczka Michal]

> -Original Message-
> From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, May 05, 2004 2:14 AM
> To: Maven Developers List
> Subject: RE: xdoc with custom templates and/or navigation
> 
> 
> On Tue, 2004-05-04 at 20:07, Brett Porter wrote:
> > The wiki has instructions on submitting patches.
> > 
> > You need to do cvs diff -u against CVS HEAD for 
> maven-plugins/xdoc, ie:
> > 
> > 1. cvs checkout maven-plugins
> > 2. make changes in xdoc plugin there
> > 3. create issue in JIRA (MPXDOC- returned)
> > 4. do this:
> > cd maven-plugins
> > cvs diff -u xdoc >MPXDOC-.diff
> > 5. attach MPXDOC-.diff to the issue
> > 6. wait for it to be applied
> > 
> > Remember to change  to the number given by JIRA.
> > 
> > But on a side note - I'm not exactly sure why you want to 
> override these?
> 
> It's not one I'd like to see applied. Changing the structure of the
> output is not a good idea. If required I think it's just indicative of
> the stylesheet lacking certain elements. The application of the theme
> should be entirely possible via the stylesheets. If you want 
> completely
> different output then do it with something else. This is not 
> the sort of
> customization I want to see in any of the plugins.
> 
> -- 
> jvz.
> 

Jason!


It's not just a question of the "theme".
Some organization have already their own standards which define precisly how
their intranet pages are looking.
Often thy have alredy hundreds of pages with spcific layout
which is completly different then this one which proposed by maven (for
example some of them are using html frames) 
For them it might not only be attrative but simply necessry to have much
higher level of customization which will allow to generate what they want.

I understand that you intention is to have quite simillar (standard) sites
which are easy to browse. It's an appealing goal
but I think that most of the users will use the default theme anyway. But if
somebody cannot do this or he does not want he should  be
free to go with his own solution. 

BTW: in maven1 there are strange relations between site and xdoc plugins. We
might imagine that somebody will be able to write his own replecment
for xdoc plugin and use it from site plugin.


Michal


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

[jira] Commented: (MPCHANGELOG-38) changelog does not work with cvsnt

[jira]

The following comment has been added to this issue:

 Author: Archimedes Trajano
Created: Wed, 5 May 2004 4:35 AM
   Body:
Yup I have read that document which details what you have to do if you are using cvsnt 
client to connect to a cvs server. This is a different problem though, this is a 
problem with the CVS server itself.  Though I suspect it may be from the cvslib 
library since it seems to disregard dontUseGZip when it is set on the client and 
setGZipEnabled(false) on the GlobalOptions.  I tried to modify the plugin on my system 
to see if it was an easy fix.

I have upgraded to the latest versions of CVSNT

Client: Concurrent Versions System (CVSNT) 2.0.41 (client/server)
Server: Concurrent Versions System (CVSNT) 2.0.41 (client/server)

And it still has the same problem.

Also regarding the document, the create-cvspass does not create the password file 
properly, it only puts in the password with no option to specify the path.  I think 
this cvspass function should be offloaded to a separate plugin called cvs or maybe to 
scm?  I'll be creating another jira bug for this if you think its worth while.
-
View this comment:
  
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPCHANGELOG-38&page=comments#action_19379

-
View the issue:
  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPCHANGELOG-38

Here is an overview of the issue:
-
Key: MPCHANGELOG-38
Summary: changelog does not work with cvsnt
   Type: Bug

 Status: Unassigned
   Priority: Major

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

Project: maven-changelog-plugin
   Versions:
 1.5

   Assignee: 
   Reporter: Archimedes Trajano

Created: Tue, 4 May 2004 1:35 PM
Updated: Wed, 5 May 2004 4:35 AM
Environment: CVSNT 2.0.26

Description:
C:\Projects\pensions>maven maven-changelog-plugin:report
 __  __
|  \/  |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \  ~ intelligent projects ~
|_|  |_\__,_|\_/\___|_||_|  v. 1.0-rc3-SNAPSHOT

build:start:

maven-changelog-plugin:report:
[echo] Generating the changelog report
Server is not supporting gzip-file-contents request
ChangeLog found: 0 entries
BUILD SUCCESSFUL
Total time: 5 seconds
Finished at: Tue May 04 19:27:12 CEST 2004



-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


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

[jira] Commented: (MAVEN-1216) NoClassDefFoundError for org/jaxen/JaxenException and org/saxpath/SAXPathException

[jira]

The following comment has been added to this issue:

 Author: Christian Stein
Created: Wed, 5 May 2004 4:17 AM
   Body:
Is there any workaround for this?
-
View this comment:
  
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1216&page=comments#action_19378

-
View the issue:
  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1216

Here is an overview of the issue:
-
Key: MAVEN-1216
Summary: NoClassDefFoundError for org/jaxen/JaxenException  and 
org/saxpath/SAXPathException
   Type: Bug

 Status: Closed
   Priority: Major
 Resolution: CANNOT REPRODUCE

 Original Estimate: 1 hour
 Time Spent: Unknown
  Remaining: 1 hour

Project: maven
 Components: 
 jelly/ant integration
   Versions:
 1.0-rc2

   Assignee: Brett Porter
   Reporter: Vladimir Kralik

Created: Thu, 1 Apr 2004 9:51 AM
Updated: Wed, 5 May 2004 4:17 AM
Environment: maven-1.0-rc2
jdk 1.4.2_03
M$ Windows 2000 SP 4
cygwin

Description:
When I try install my own plugin ( by using "maven plugin:install" ),then I get :
<>
Caused by: java.lang.NoClassDefFoundError: org/jaxen/JaxenException
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:141)
at 
org.apache.commons.jelly.tags.xml.XMLTagLibrary.class$(XMLTagLibrary.java:82)
<>

after "cp jaxen-core-1.0-FCS.jar $MAVEN_HOME/lib" :

<>
Caused by: java.lang.NoClassDefFoundError: org/saxpath/SAXPathException
<>>
at 
org.apache.commons.jelly.tags.xml.XMLTagLibrary.class$(XMLTagLibrary.java:82)
<>

after "cp saxpath-1.0-FCS.jar $MAVEN_HOME/lib"

it works fine.

jaxen and saxpath are not listed as dependecies in my plugin.
I use very simple Hello World plugin ( see below )

I thing that problem is in jelly-integration, because jelly 
(org.apache.commons.jelly.tags.xml.ForEachTag) requires org.jaxen.JaxenException and 
dom4j (org.dom4j.xpath.XPathPattern) requieres org.saxpath.SAXPathException.

===
project.xml
===


  3
  maven-hello-plugin
  Maven Hello World Plug-in
  1.0.0-SNAPSHOT
  
  

  
${basedir}

  plugin.jelly
  plugin.properties
  project.xml

  

  

===
plugin.jelly
===



Hello, ${maven.hello.world}


===
plugin.properties
===
maven.hello.world=World


-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


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

[jira] Commented: (MAVEN-1266) Please upload easymock 1.1 on ibiblio

[jira]

The following comment has been added to this issue:

 Author: nicolas de loof
Created: Wed, 5 May 2004 4:13 AM
   Body:
Sorry, didn't see they're is a dedicated project (they're so much maven-xxx !)
-
View this comment:
  
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1266&page=comments#action_19377

-
View the issue:
  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1266

Here is an overview of the issue:
-
Key: MAVEN-1266
Summary: Please upload easymock 1.1 on ibiblio
   Type: Wish

 Status: Closed
   Priority: Major
 Resolution: FIXED

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

Project: maven

   Assignee: 
   Reporter: nicolas de loof

Created: Wed, 5 May 2004 3:45 AM
Updated: Wed, 5 May 2004 4:13 AM

Description:
Please upload new 1.1 version of easymock to ibiblio.
It adds support for mocking classes (not just intefaces)


-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


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

[jira] Closed: (MAVEN-1266) Please upload easymock 1.1 on ibiblio

[jira]

Message:

   The following issue has been closed.

   Resolver: Emmanuel Venisse
   Date: Wed, 5 May 2004 4:05 AM

Done. The next time, could you use the correct project under Jira (MAVENUPLOAD). Thanks
-
View the issue:
  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1266

Here is an overview of the issue:
-
Key: MAVEN-1266
Summary: Please upload easymock 1.1 on ibiblio
   Type: Wish

 Status: Closed
   Priority: Major
 Resolution: FIXED

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

Project: maven

   Assignee: 
   Reporter: nicolas de loof

Created: Wed, 5 May 2004 3:45 AM
Updated: Wed, 5 May 2004 4:05 AM

Description:
Please upload new 1.1 version of easymock to ibiblio.
It adds support for mocking classes (not just intefaces)


-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


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

[jira] Closed: (MAVENUPLOAD-103) Please upload easymock 1.1 and EasyMock Class Extension 1.1

[jira]

Message:

   The following issue has been closed.

   Resolver: Emmanuel Venisse
   Date: Wed, 5 May 2004 4:04 AM

Done.
-
View the issue:
  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVENUPLOAD-103

Here is an overview of the issue:
-
Key: MAVENUPLOAD-103
Summary: Please upload easymock 1.1 and EasyMock Class Extension 1.1
   Type: Task

 Status: Closed
   Priority: Major
 Resolution: FIXED

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

Project: maven-upload-requests

   Assignee: Jason van Zyl
   Reporter: Julien Kirch

Created: Tue, 4 May 2004 10:16 AM
Updated: Wed, 5 May 2004 4:04 AM

Description:
http://www.easymock.org/easymock1.1.zip
http://www.easymock.org/easymockclassextension1.1.zip
thanks



-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


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

[jira] Commented: (MAVEN-1266) Please upload easymock 1.1 on ibiblio

[jira]

The following comment has been added to this issue:

 Author: nicolas de loof
Created: Wed, 5 May 2004 3:54 AM
   Body:
Just notice class mocking support is an optional extension to easymock, also in 1.1 
version

http://easymock.org/Downloads.html
-
View this comment:
  
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1266&page=comments#action_19374

-
View the issue:
  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1266

Here is an overview of the issue:
-
Key: MAVEN-1266
Summary: Please upload easymock 1.1 on ibiblio
   Type: Wish

 Status: Unassigned
   Priority: Major

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

Project: maven

   Assignee: 
   Reporter: nicolas de loof

Created: Wed, 5 May 2004 3:45 AM
Updated: Wed, 5 May 2004 3:54 AM

Description:
Please upload new 1.1 version of easymock to ibiblio.
It adds support for mocking classes (not just intefaces)


-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


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

[jira] Created: (MAVEN-1266) Please upload easymock 1.1 on ibiblio

[jira]

Message:

  A new issue has been created in JIRA.

-
View the issue:
  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1266

Here is an overview of the issue:
-
Key: MAVEN-1266
Summary: Please upload easymock 1.1 on ibiblio
   Type: Wish

 Status: Unassigned
   Priority: Major

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

Project: maven

   Assignee: 
   Reporter: nicolas de loof

Created: Wed, 5 May 2004 3:45 AM
Updated: Wed, 5 May 2004 3:45 AM

Description:
Please upload new 1.1 version of easymock to ibiblio.
It adds support for mocking classes (not just intefaces)


-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


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

cvs commit: maven-plugins/xdoc/xdocs changes.xml faq.fml

[brett]

brett   2004/05/05 00:38:31

  Modified:xdoc plugin.jelly plugin.properties
   xdoc/src/plugin-resources site.jsl
   xdoc/xdocs changes.xml faq.fml
  Log:
  o exclude fml files in copy
  o easier use of classic that always works
  
  Revision  ChangesPath
  1.59  +1 -0  maven-plugins/xdoc/plugin.jelly
  
  Index: plugin.jelly
  ===
  RCS file: /home/cvs/maven-plugins/xdoc/plugin.jelly,v
  retrieving revision 1.58
  retrieving revision 1.59
  diff -u -r1.58 -r1.59
  --- plugin.jelly  2 May 2004 10:16:08 -   1.58
  +++ plugin.jelly  5 May 2004 07:38:30 -   1.59
  @@ -583,6 +583,7 @@
 
   
 
  +  
 
 
   
  
  
  
  1.20  +1 -0  maven-plugins/xdoc/plugin.properties
  
  Index: plugin.properties
  ===
  RCS file: /home/cvs/maven-plugins/xdoc/plugin.properties,v
  retrieving revision 1.19
  retrieving revision 1.20
  diff -u -r1.19 -r1.20
  --- plugin.properties 3 May 2004 23:51:22 -   1.19
  +++ plugin.properties 5 May 2004 07:38:30 -   1.20
  @@ -25,6 +25,7 @@
   
   maven.xdoc.crumb.separator=|
   maven.xdoc.theme.url=
  +maven.xdoc.theme=theme
   
   # Location where the artifacts are distributed. This property is optional. 
   # If it is not defined, then the Download report will not be added to the 
  
  
  
  1.57  +1 -1  maven-plugins/xdoc/src/plugin-resources/site.jsl
  
  Index: site.jsl
  ===
  RCS file: /home/cvs/maven-plugins/xdoc/src/plugin-resources/site.jsl,v
  retrieving revision 1.56
  retrieving revision 1.57
  diff -u -r1.56 -r1.57
  --- site.jsl  3 May 2004 23:51:22 -   1.56
  +++ site.jsl  5 May 2004 07:38:31 -   1.57
  @@ -60,7 +60,7 @@
@import url("${maven.xdoc.theme.url}");
]]>

cvs commit: maven-plugins/xdocs index.xml

[brett]

brett   2004/05/05 00:36:03

  Added:   xdocsindex.xml
  Log:
  site updates
  
  Revision  ChangesPath
  1.1  maven-plugins/xdocs/index.xml
  
  Index: index.xml
  ===
  
  
  
  
  
  

  Maven plugins
  Emmanuel Venisse

  

  

  This page contains a list of known plugins site. We would be
  very interested if you would drop us a note if you are creating
  a Maven plugin and would like to be added to this list.


  

  Maven plugins

  


  

  http://jakarta.apache.org/cactus/integration/maven/";>Cactus 
plugin
  Plugin for Cactus

  


  

  http://www.codeczar.com/products/maven-ejbgen-plugin/";>Weblogic EJBGen 
plugin
  Plugin for Weblogic EJBGen

  


  

  http://maven-plugins.sourceforge.net/";>Maven-Plugins
  Various plugins 


  http://maven-validator.sourceforge.net/";>Maven 
Validator
  Validates XHTML


  http://xdoclet.sourceforge.net/maven-plugin.html";>XDoclet 
plugin
  Plugin for XDoclet


  http://maven-taglib.sourceforge.net/";>Maven Taglib 
plugin
  Taglib Plug-in is a maven plugin for jsp tag libraries 
developers

  


  

  http://statcvs-xml.berlios.de/";>StatCvs-XML plugin
  Plugin for StatCvs-XML

  

  
  

  
http://mevenide.sourceforge.net/";>Mevenide
Mevenide (Maven IDE Integration) aims at integrating Maven into 
standard IDEs. Currently only Eclipse is targeted.
  

  

  
  
  
  

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

cvs commit: maven-plugins/xdocs navigation.xml faq.fml index.html

[brett]

brett   2004/05/05 00:34:38

  Modified:.project.xml project.properties
   xdocsnavigation.xml faq.fml
  Removed: .README.txt
   xdocsindex.html
  Log:
  site updates
  
  Revision  ChangesPath
  1.20  +1 -1  maven-plugins/project.xml
  
  Index: project.xml
  ===
  RCS file: /home/cvs/maven-plugins/project.xml,v
  retrieving revision 1.19
  retrieving revision 1.20
  diff -u -r1.19 -r1.20
  --- project.xml   1 May 2004 09:53:54 -   1.19
  +++ project.xml   5 May 2004 07:34:37 -   1.20
  @@ -35,7 +35,7 @@
   
 
http://jira.codehaus.org/BrowseProject.jspa?id=10030
 maven.apache.org
  -  /www/maven.apache.org/reference/plugins/optional/
  +  /www/maven.apache.org/reference/plugins/
 www.ibiblio.org
 /public/html/maven/maven/plugins/
   
  
  
  
  1.13  +3 -3  maven-plugins/project.properties
  
  Index: project.properties
  ===
  RCS file: /home/cvs/maven-plugins/project.properties,v
  retrieving revision 1.12
  retrieving revision 1.13
  diff -u -r1.12 -r1.13
  --- project.properties2 May 2004 18:05:39 -   1.12
  +++ project.properties5 May 2004 07:34:37 -   1.13
  @@ -32,7 +32,7 @@
   
   # Multiproject plugin settings
   maven.multiproject.navigation=independent
  -maven.multiproject.overviewPage.title=Maven Optional Plugins
  -maven.multiproject.overviewPage.link=optional
  -maven.multiproject.overviewPage.text=The following plugins are optional
  +maven.multiproject.overviewPage.title=Maven Plugins
  +maven.multiproject.overviewPage.link=plugins
  +maven.multiproject.overviewPage.text=The following Maven plugins are available:
   maven.multiproject.excludes=plugin-parent/project.xml
  
  
  
  1.5   +1 -2  maven-plugins/xdocs/navigation.xml
  
  Index: navigation.xml
  ===
  RCS file: /home/cvs/maven-plugins/xdocs/navigation.xml,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- navigation.xml4 Mar 2004 18:39:50 -   1.4
  +++ navigation.xml5 May 2004 07:34:38 -   1.5
  @@ -25,12 +25,11 @@
   
   
 http://maven.apache.org/index.html"/>
  -  
   
  
 
  +  
 
  -  
   
 
   
  
  
  
  1.7   +10 -2 maven-plugins/xdocs/faq.fml
  
  Index: faq.fml
  ===
  RCS file: /home/cvs/maven-plugins/xdocs/faq.fml,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -u -r1.6 -r1.7
  --- faq.fml   4 Mar 2004 18:39:50 -   1.6
  +++ faq.fml   5 May 2004 07:34:38 -   1.7
  @@ -53,6 +53,14 @@
 
   
   
  +
  +  How do I generate the dashboard for all plugins?
  +  
  +maven dashboard
  +  
  +
  +
 
 
  -
  \ No newline at end of file
  +
  +
  
  
  

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

cvs commit: maven/src/java/org/apache/maven/plugin PluginManager.java

[brett]

brett   2004/05/05 00:29:28

  Modified:src/java/org/apache/maven/plugin Tag: MAVEN-1_0-BRANCH
PluginManager.java
  Log:
  logging
  
  Revision  ChangesPath
  No   revision
  No   revision
  1.70.4.43 +2 -1  maven/src/java/org/apache/maven/plugin/PluginManager.java
  
  Index: PluginManager.java
  ===
  RCS file: /home/cvs/maven/src/java/org/apache/maven/plugin/PluginManager.java,v
  retrieving revision 1.70.4.42
  retrieving revision 1.70.4.43
  diff -u -r1.70.4.42 -r1.70.4.43
  --- PluginManager.java28 Apr 2004 03:28:57 -  1.70.4.42
  +++ PluginManager.java5 May 2004 07:29:28 -   1.70.4.43
  @@ -419,6 +419,7 @@
   }
   else
   {
  +log.debug( "adding dependency " + artifact.getFile() + " 
into project classloader" );
   projectClassLoader.addURL( artifact.getFile().toURL() );
   }
   }
  
  
  

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

cvs commit: maven/maven-jelly-tags project.xml

[brett]

brett   2004/05/05 00:27:57

  Modified:.Tag: MAVEN-1_0-BRANCH project.properties
project.xml
   maven-jelly-tags Tag: MAVEN-1_0-BRANCH project.xml
  Log:
  reporting
  
  Revision  ChangesPath
  No   revision
  No   revision
  1.51.2.24 +1 -14 maven/project.properties
  
  Index: project.properties
  ===
  RCS file: /home/cvs/maven/project.properties,v
  retrieving revision 1.51.2.23
  retrieving revision 1.51.2.24
  diff -u -r1.51.2.23 -r1.51.2.24
  --- project.properties2 May 2004 18:31:32 -   1.51.2.23
  +++ project.properties5 May 2004 07:27:57 -   1.51.2.24
  @@ -66,19 +66,6 @@
   maven.xdoc.version = ${pom.currentVersion}
   
   #--
  -# M U L T I P R O J E C T  -  A L L  P L U G I N G S
  -#--
  -maven.multiproject.basedir=${maven.plugins.directory}
  -#do not go down to nested subproject
  -maven.multiproject.includes=${maven.plugins.includes}
  -maven.multiproject.excludes=${maven.plugins.excludes}
  -maven.multiproject.navigation=independent
  -maven.multiproject.overviewPage.title=Maven Core Plugins
  -maven.multiproject.overviewPage.link=reference/plugins/core-plugins
  -#maven.multiproject.overviewPage.linkTitle=Plugins
  -maven.multiproject.overviewPage.text=The following plugins are provided along with 
Maven
  -
  -#--
   # N S I S   P R O P E R T I E S
   #--
   maven.nsis.src=${basedir}/src/installer/nsis
  @@ -143,4 +130,4 @@
   
   # jdk1.3 compat
   maven.junit.fork=yes
  -maven.junit.sysproperties=maven.home
  \ No newline at end of file
  +maven.junit.sysproperties=maven.home
  
  
  
  1.317.4.22 +0 -1  maven/project.xml
  
  Index: project.xml
  ===
  RCS file: /home/cvs/maven/project.xml,v
  retrieving revision 1.317.4.21
  retrieving revision 1.317.4.22
  diff -u -r1.317.4.21 -r1.317.4.22
  --- project.xml   3 May 2004 23:59:42 -   1.317.4.21
  +++ project.xml   5 May 2004 07:27:57 -   1.317.4.22
  @@ -795,7 +795,6 @@
   maven-pmd-plugin
   maven-simian-plugin
   maven-faq-plugin
  -maven-multiproject-plugin
 
 
   
  
  
  
  No   revision
  No   revision
  1.1.2.4   +0 -1  maven/maven-jelly-tags/Attic/project.xml
  
  Index: project.xml
  ===
  RCS file: /home/cvs/maven/maven-jelly-tags/Attic/project.xml,v
  retrieving revision 1.1.2.3
  retrieving revision 1.1.2.4
  diff -u -r1.1.2.3 -r1.1.2.4
  --- project.xml   3 May 2004 23:59:42 -   1.1.2.3
  +++ project.xml   5 May 2004 07:27:57 -   1.1.2.4
  @@ -229,7 +229,6 @@
   maven-pmd-plugin
   maven-simian-plugin
   maven-faq-plugin
  -maven-multiproject-plugin
 
   
   
  
  
  

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

cvs commit: maven/xdocs/reference/plugins index.xml

[brett]

brett   2004/05/05 00:18:51

  Modified:xdocsTag: MAVEN-1_0-BRANCH development-process.xml
navigation.xml
  Added:   maven-jelly-tags/xdocs Tag: MAVEN-1_0-BRANCH index.xml
  Removed: xdocs/reference/plugins Tag: MAVEN-1_0-BRANCH index.xml
  Log:
  doco updates
  
  Revision  ChangesPath
  No   revision
  No   revision
  1.1.2.1   +41 -0 maven/maven-jelly-tags/xdocs/Attic/index.xml
  
  
  
  
  No   revision
  No   revision
  1.7.4.2   +1 -1  maven/xdocs/development-process.xml
  
  Index: development-process.xml
  ===
  RCS file: /home/cvs/maven/xdocs/development-process.xml,v
  retrieving revision 1.7.4.1
  retrieving revision 1.7.4.2
  diff -u -r1.7.4.1 -r1.7.4.2
  --- development-process.xml   4 Mar 2004 17:45:56 -   1.7.4.1
  +++ development-process.xml   5 May 2004 07:18:51 -   1.7.4.2
  @@ -66,7 +66,7 @@
   
 
 
  -Modifying Plugins
  +Modifying 
Plugins
   
 Provides some guidelines to use when modifying plugins. This 
 includes steps that contributors and committers should follow.
  
  
  
  1.33.4.6  +1 -0  maven/xdocs/navigation.xml
  
  Index: navigation.xml
  ===
  RCS file: /home/cvs/maven/xdocs/navigation.xml,v
  retrieving revision 1.33.4.5
  retrieving revision 1.33.4.6
  diff -u -r1.33.4.5 -r1.33.4.6
  --- navigation.xml29 Mar 2004 00:10:27 -  1.33.4.5
  +++ navigation.xml5 May 2004 07:18:51 -   1.33.4.6
  @@ -47,6 +47,7 @@
   
   
   
  +
   
 
   
  
  
  

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