cvs commit: maven-plugins/scm/xdocs changes.xml

2004-11-28 Thread carlos
carlos  2004/11/28 02:54:12

  Modified:scm  plugin.jelly
   scm/xdocs changes.xml
  Log:
  Ignore POM if the scm root is specified in command line
  
  Revision  ChangesPath
  1.16  +7 -0  maven-plugins/scm/plugin.jelly
  
  Index: plugin.jelly
  ===
  RCS file: /home/cvs/maven-plugins/scm/plugin.jelly,v
  retrieving revision 1.15
  retrieving revision 1.16
  diff -u -r1.15 -r1.16
  --- plugin.jelly  9 Aug 2004 01:25:46 -   1.15
  +++ plugin.jelly  28 Nov 2004 10:54:12 -  1.16
  @@ -35,6 +35,13 @@
 !-- Goal to validate SCM properties  --
 !--==--
 goal name=scm:parse-connection
  +
  +!-- ignore POM if the scm root is specified in command line --
  +j:if test=${!empty(context.getVariable('maven.scm.cvs.root')) ||
  +  !empty(context.getVariable('maven.scm.svn.root'))}
  +  j:set var=maven.scm.ignore.pom.connection value=true/
  +/j:if
  +
   j:set var=checkValue value=${maven.scm.ignore.pom.connection}/
   j:if test=${!checkValue}
 j:set var=checkValue 
value=${maven.scm.ignore.pom.developerConnection}/
  
  
  
  1.20  +1 -0  maven-plugins/scm/xdocs/changes.xml
  
  Index: changes.xml
  ===
  RCS file: /home/cvs/maven-plugins/scm/xdocs/changes.xml,v
  retrieving revision 1.19
  retrieving revision 1.20
  diff -u -r1.19 -r1.20
  --- changes.xml   9 Aug 2004 01:25:47 -   1.19
  +++ changes.xml   28 Nov 2004 10:54:12 -  1.20
  @@ -26,6 +26,7 @@
 body
   release version=1.4.2-SNAPSHOT date=in CVS
 action dev=dion type=fix issue=MPSCM-25Ignore whitespace when 
creating a patch/action
  +  action dev=carlos type=fixIgnore POM if the scm root is 
specified in command line/action
   /release
   
   release version=1.4.1 date=2004-07-30
  
  
  

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



[jira] Created: (MAVENUPLOAD-266) Upload of NekoHTML 0.9.4

2004-11-28 Thread jira
Message:

  A new issue has been created in JIRA.

-
View the issue:
  http://jira.codehaus.org/browse/MAVENUPLOAD-266

Here is an overview of the issue:
-
Key: MAVENUPLOAD-266
Summary: Upload of NekoHTML 0.9.4
   Type: Task

 Status: Unassigned

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

Project: maven-upload-requests

   Assignee: 
   Reporter: Chris Erskine

Created: Sun, 28 Nov 2004 9:58 AM
Updated: Sun, 28 Nov 2004 9:58 AM

Description:
http://sourceforge.net/tracker/download.php?group_id=47038atid=448268file_id=110389aid=1074656

http://www.apache.org/~andyc/neko/doc/html/index.html

Upload of new version of HekoHTML to allow it to be used by HtmlUnit


-
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]



one more time: [sitemultiproject plugins] - reorganization of goals used to generate sites

2004-11-28 Thread Michal Maczka
Sometime I ago I have proposed some changes in site  multiproject plugins.
I could not apply them at that time as we were releasing  1.0.1 version.
Somebody has any objections against those changes (they are described 
below)?

Michal
Hi!
Recently I've trying to generate multilevel sites using multiproject plugin
and I have problems with  that approach
due to some strange relationships between goals in multiproject and site
plugins
What I am trying to do exactly is to run site:generate goal if project is
a leaf in a project tree or multiprojct:site in other case.
( I am using maven.xml file for controlling that
  goal name=site
   attainGoal name=multiproject:site/
/goal
)
I would like change both multiproject and site plugin to make it possible
- In site plugin:
I would like to attain site:generate goal from site goal - not other way
around
- in multiproject plugin at the end of the code of the goal 

 goal name=multiproject:site
 /goal
I would like to attain site:generate goal - not site goal. 

I wonder if 

a) it will be still possible to include those changes in 1.0.1 release?
b) am I missing something and this will brake something or will not work? I
tested it locally and it seems to be working for me...
regards
Michal
 

--
Startuj z INTERIA.PL!!!  http://link.interia.pl/f1837
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Re: one more time: [sitemultiproject plugins] - reorganization of goals used to generate sites

2004-11-28 Thread Brett Porter
Michal Maczka wrote:
Sometime I ago I have proposed some changes in site  multiproject 
plugins.
I could not apply them at that time as we were releasing  1.0.1 version.
Somebody has any objections against those changes (they are described 
below)?

Actually, there was still some confusion about whether this was 
necessary. I'd like to avoid needing to override goals. See below:

- In site plugin:
I would like to attain site:generate goal from site goal - not 
other way
around

+1, it seems wrong anyway. There should also be a site:site goal.
- in multiproject plugin at the end of the code of the goal
 goal name=multiproject:site
 /goal
I would like to attain site:generate goal - not site goal.

I'd prefer for this that the site goal was customisable.
maven.multiproject.site.goal=site
Then you can do
maven.multiproject.site.goal=site
or
maven.multiproject.site.goal=multiproject:site
depending on the context.
As a more general case, perhaps we should have:
maven.multiproject.type=multiproject
and flip that to multiproject:site automatically. This will also make 
multiproject:install, etc recurse properly. WDYT?

I wonder if
a) it will be still possible to include those changes in 1.0.1 release?

As a side note, these probably won't be included in 1.0.2 either as 
that, at this stage, seems to be only core changes to fix regressions.

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


[jira] Commented: (MPDIST-17) should be able to turn off creation of zip and.or tar.gz files via plugin properties

2004-11-28 Thread jira
The following comment has been added to this issue:

 Author: dion gillard
Created: Mon, 29 Nov 2004 12:40 AM
   Body:
I'll just agree to disagree here then.
-
View this comment:
  http://jira.codehaus.org/browse/MPDIST-17?page=comments#action_27243

-
View the issue:
  http://jira.codehaus.org/browse/MPDIST-17

Here is an overview of the issue:
-
Key: MPDIST-17
Summary: should be able to turn off creation of zip and.or tar.gz files via 
plugin properties
   Type: Improvement

 Status: Open
   Priority: Major

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

Project: maven-dist-plugin

   Assignee: Brett Porter
   Reporter: Ian P. Springer

Created: Wed, 24 Nov 2004 7:49 PM
Updated: Mon, 29 Nov 2004 12:40 AM
Environment: n/a

Description:
For our project, we want to only make our dist available as a zipfile. This is 
because it is a Java project, and therefore we know the jar command will always 
be available to our users to unzip the distribution, no matter what platform 
they are on. So here is no need for a tar.gz dist. Unfortunately, it is 
currently not possible to turn off creation of the tar.gz. Can you please add 
some properties to control this? Something like:

maven.dist.create.zip = true
maven.dist.create.tar.gz = true

Thanks.
Ian



-
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/xdocs/using repositories.xml tests.xml

2004-11-28 Thread brett
brett   2004/11/28 22:58:54

  Modified:xdocsfaq.fml index.xml navigation.xml
   xdocs/about whymaven.xml
   xdocs/developers building-from-source.xml
   xdocs/development branches.xml
   xdocs/reference articles.xml sharing-plugins.xml
   xdocs/start adapting.xml quick-start.xml
   xdocs/using repositories.xml tests.xml
  Log:
  some cleanup
  
  Revision  ChangesPath
  1.12  +4 -1  maven/xdocs/faq.fml
  
  Index: faq.fml
  ===
  RCS file: /home/cvs/maven/xdocs/faq.fml,v
  retrieving revision 1.11
  retrieving revision 1.12
  diff -u -r1.11 -r1.12
  --- faq.fml   22 Nov 2004 11:59:53 -  1.11
  +++ faq.fml   29 Nov 2004 06:58:54 -  1.12
  @@ -492,7 +492,10 @@
   
 part id=ant
   titleAnt/title
  -!-- TODO:
  +!-- TODO: actually, don't think this belongs here
  +- move getting help to start/quick-start.html
  +- Ant scripts goes to migrating
  +- all of these are linked from this faq briefly
   section name=Calling Ant Scripts from Maven
 p
   Often, people want to get their feet wet with Maven by using it to 
do the standard things, but to use their
  
  
  
  1.17  +4 -8  maven/xdocs/index.xml
  
  Index: index.xml
  ===
  RCS file: /home/cvs/maven/xdocs/index.xml,v
  retrieving revision 1.16
  retrieving revision 1.17
  diff -u -r1.16 -r1.17
  --- index.xml 22 Nov 2004 11:59:54 -  1.16
  +++ index.xml 29 Nov 2004 06:58:54 -  1.17
  @@ -26,15 +26,13 @@
   
 body
   section name=Welcome to Maven
  -  subsection name=About Maven
  -p
  +  p
   Maven is a software project management and comprehension tool. Based 
on the concept of a project object model
   (a href=reference/glossary.html#POMPOM/a), Maven can manage a 
project's build, reporting and documentation from
   a central piece of information.
  -/p
  -  /subsection
  +  /p
   
  -  subsection name=Using Maven
  +  subsection name=Getting Started with Maven
   p
 bNeed Maven to build a project you have downloaded?/b
   /p
  @@ -56,9 +54,6 @@
   p
 Read our a href=start/maven-for-ant-users.htmlMaven for Ant 
Users/a explanatory document.
   /p
  -  !-- TODO: Other ideas here: visual tour (walk through the web 
site),
  -  why maven (objectives, features and the stuff below), complete 
user guide,
  -  plugin developers guide, and Maven developers area --
 /subsection
   
 subsection name=Help and Feedback
  @@ -71,3 +66,4 @@
   /section
 /body
   /document
  +
  
  
  
  1.51  +15 -24maven/xdocs/navigation.xml
  
  Index: navigation.xml
  ===
  RCS file: /home/cvs/maven/xdocs/navigation.xml,v
  retrieving revision 1.50
  retrieving revision 1.51
  diff -u -r1.50 -r1.51
  --- navigation.xml22 Nov 2004 12:18:05 -  1.50
  +++ navigation.xml29 Nov 2004 06:58:54 -  1.51
  @@ -42,9 +42,8 @@
   
   menu name=About Maven
 item name=What is Maven? 
href=/about/whatismaven.html /
  -  item name=What is Maven Not? 
href=/about/whatismaven.html#What_is_Maven_Not_ /
  +  item name=Why use Maven? 
href=/about/whymaven.html /
 item name=Feature Summary
href=/about/features.html /
  -  item name=Why Maven? 
href=/about/whymaven.html / !-- TODO: needed? Not linked from anywhere, no 
content for it yet --
 item name=Powered by Maven   href=/about/powered.html 
/
   /menu
   
  @@ -61,19 +60,13 @@
 item name=Building a Project Web Sitehref=/using/site.html /
 item name=Working with Web Applications  href=/using/war.html /
 item name=Customising Maven  
href=/using/customising.html / !-- TODO: write about properties, maven.xml 
--
  +  item name=Making Releases
href=/using/releasing.html /
 item name=Best Practices 
href=/using/bestpractices.html /
 item name=Migrating from Ant 
href=/using/migrating.html / !-- TODO: will this really be different from 
Adapting? --
 item name=FAQhref=/faq.html /
 item name=Writing a Plugin   
href=/using/developing-plugins.html /
   !-- TODO: not the right section or name... --
 item name=Working with Repositories  
href=/using/repositories.html /
  -!-- TODO: write about (Mevenide, console running, generating projects)
  -... or farm out to mevenide completely?
  -  item name=IDE Integrationhref=/using/ide.html 
collapse=true
  -item