RE : [vote] Release Maven Site plugin 2.0-beta-5
Hi,
Not a maven dev but a user who made some tests ;-).
Today,
I made this :
rm -rf $HOME/.m2/repository/*
mvn -P snapshots -U clean site site:deploy (snapshots profile included
snapshots in apache and codehaus)
I have the stack trace :
[INFO] Generate Dependencies report.
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] null
[INFO]
[INFO] Trace
java.lang.NullPointerException
at
org.apache.maven.report.projectinfo.ReportResolutionListener$Node.access
$000(ReportResolu
tionListener.java:149)
at
org.apache.maven.report.projectinfo.ReportResolutionListener.manageArtif
act(ReportResolut
ionListener.java:121)
at
org.apache.maven.artifact.resolver.DefaultArtifactCollector.fireEvent(De
faultArtifactColl
ector.java:408)
Glurspp ;-)
In my case it's a multi module site.
The root site is well generated and deployed but failed on the first
module.
Any idea ? (do you need more information on poms or something else ? )
Thanks,
-Olivier
-Message d'origine-
De : Brett Porter [mailto:[EMAIL PROTECTED]
Envoyé : mercredi 10 mai 2006 20:21
À : Maven Developers List
Objet : [vote] Release Maven Site plugin 2.0-beta-5
Hi,
There's a wealth of new features here.
(snapshot pending svn.apache.org coming back up, also I have the docs
here to commit then too)
[ ] +1
[ ] +0
[ ] -1
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11146styleNa
me=Textversion=12541
* [MSITE-23] - problems with site:stage
* [MSITE-24] - Site deployment doesn't allow users in the group to write
files
* [MSITE-40] - don't generate doc file if it is unchanged
* [MSITE-44] - make site reactor aware
* [MSITE-48] - add reusable skin functionality and create skins default,
stylus and classic
* [MSITE-51] - add breadcrumbs
* [MSITE-58] - Ability to assign a report to choosen navigation menu
* [MSITE-65] - ${parentProject}\ in default site descriptor doesn't
resolve
* [MSITE-71] - Plugin uses NON interpolated model values (e.g URL) due
to MavenProject.getParent returning non interpolated project
* [MSITE-72] - new non reactor populateModules SiteMojo code assumes
each POM declares its own URL
* [MSITE-73] - new site code fails to generate banner images in projects
other than site.xml owning project
* [MSITE-74] - Suport proxy
* [MSITE-86] - ${modules} macro placed in site.xml does work properly
* [MSITE-91] - src/site/site.xml hardcoded in AbstractSiteMojo.java
* [MSITE-97] - Site plugin doesn't copy images to target
* [MSITE-102] - SCM files in src/site directory cause 'mvn site' to fail
- need to exclude files
* [MSITE-104] - There is no way to specify the input encoding of site
documents
* [MSITE-108] - problem with nav generation (collapse = true) snapshot
used 20060315.092459-4.jar (same trouble doxia trunk)
* [MSITE-110] - Use reactor to find parent URL where possible patch
(patch also includes improved calculate relative path and better read
modules from filesystem POM functionality)
* [MSITE-111] - Invalid site-plugin_ja.properties
* [MSITE-113] - generated-site no longer working
* [MSITE-116] - When deploying an individual stage site it goes in the
wrong place
* [MSITE-128] - Site plugin does not properly handle filenames with more
than one period
* [MSITE-61] - deployment of site descriptor should populate any modules
items
* [MSITE-62] - make absolute paths relative where possible
* [MSITE-63] - replace interpolated values with decoration model
directives
* [MSITE-94] - Add an image in an item from the site descriptor (m1
style)
* [MSITE-100] - Improve error message about duplicate files
* [MSITE-109] - Site plugin should convert .fml files when working from
xdocDirectory
* [MSITE-115] - Provide a default value for a staging directory
* [MSITE-127] - Welcome page should work with mvn site:run
* [MSITE-68] - Ability to view how the site would look without
generating the entire site
* [MSITE-98] - Allow files to be excluded from site generation
* [MSITE-99] - Spanish translation
* [MSITE-105] - No line number for Doxia barfs makes using APT to write
site documentation all but impossible
* [MSITE-80] - refactor site mojo into reusable components
* [MSITE-103] - finish refactoring of category summary pages and index
page report
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
This e-mail, any attachments and the information contained therein (this
message) are confidential and intended solely for the use of the addressee(s).
If you have received this message in error please send it back to the sender
and delete it. Unauthorized publication, use, dissemination or disclosure of
this message, either in whole or in part is strictly prohibited.
Re: RE : [vote] Release Maven Site plugin 2.0-beta-5
I've already fixed this, but unfortunately have not been able to commit
as SVN is still down.
It just needs a null check at the location of the check
Olivier Lamy wrote:
Hi,
Not a maven dev but a user who made some tests ;-).
Today,
I made this :
rm -rf $HOME/.m2/repository/*
mvn -P snapshots -U clean site site:deploy (snapshots profile included
snapshots in apache and codehaus)
I have the stack trace :
[INFO] Generate Dependencies report.
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] null
[INFO]
[INFO] Trace
java.lang.NullPointerException
at
org.apache.maven.report.projectinfo.ReportResolutionListener$Node.access
$000(ReportResolu
tionListener.java:149)
at
org.apache.maven.report.projectinfo.ReportResolutionListener.manageArtif
act(ReportResolut
ionListener.java:121)
at
org.apache.maven.artifact.resolver.DefaultArtifactCollector.fireEvent(De
faultArtifactColl
ector.java:408)
Glurspp ;-)
In my case it's a multi module site.
The root site is well generated and deployed but failed on the first
module.
Any idea ? (do you need more information on poms or something else ? )
Thanks,
-Olivier
-Message d'origine-
De : Brett Porter [mailto:[EMAIL PROTECTED]
Envoyé : mercredi 10 mai 2006 20:21
À : Maven Developers List
Objet : [vote] Release Maven Site plugin 2.0-beta-5
Hi,
There's a wealth of new features here.
(snapshot pending svn.apache.org coming back up, also I have the docs
here to commit then too)
[ ] +1
[ ] +0
[ ] -1
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11146styleNa
me=Textversion=12541
* [MSITE-23] - problems with site:stage
* [MSITE-24] - Site deployment doesn't allow users in the group to write
files
* [MSITE-40] - don't generate doc file if it is unchanged
* [MSITE-44] - make site reactor aware
* [MSITE-48] - add reusable skin functionality and create skins default,
stylus and classic
* [MSITE-51] - add breadcrumbs
* [MSITE-58] - Ability to assign a report to choosen navigation menu
* [MSITE-65] - ${parentProject}\ in default site descriptor doesn't
resolve
* [MSITE-71] - Plugin uses NON interpolated model values (e.g URL) due
to MavenProject.getParent returning non interpolated project
* [MSITE-72] - new non reactor populateModules SiteMojo code assumes
each POM declares its own URL
* [MSITE-73] - new site code fails to generate banner images in projects
other than site.xml owning project
* [MSITE-74] - Suport proxy
* [MSITE-86] - ${modules} macro placed in site.xml does work properly
* [MSITE-91] - src/site/site.xml hardcoded in AbstractSiteMojo.java
* [MSITE-97] - Site plugin doesn't copy images to target
* [MSITE-102] - SCM files in src/site directory cause 'mvn site' to fail
- need to exclude files
* [MSITE-104] - There is no way to specify the input encoding of site
documents
* [MSITE-108] - problem with nav generation (collapse = true) snapshot
used 20060315.092459-4.jar (same trouble doxia trunk)
* [MSITE-110] - Use reactor to find parent URL where possible patch
(patch also includes improved calculate relative path and better read
modules from filesystem POM functionality)
* [MSITE-111] - Invalid site-plugin_ja.properties
* [MSITE-113] - generated-site no longer working
* [MSITE-116] - When deploying an individual stage site it goes in the
wrong place
* [MSITE-128] - Site plugin does not properly handle filenames with more
than one period
* [MSITE-61] - deployment of site descriptor should populate any modules
items
* [MSITE-62] - make absolute paths relative where possible
* [MSITE-63] - replace interpolated values with decoration model
directives
* [MSITE-94] - Add an image in an item from the site descriptor (m1
style)
* [MSITE-100] - Improve error message about duplicate files
* [MSITE-109] - Site plugin should convert .fml files when working from
xdocDirectory
* [MSITE-115] - Provide a default value for a staging directory
* [MSITE-127] - Welcome page should work with mvn site:run
* [MSITE-68] - Ability to view how the site would look without
generating the entire site
* [MSITE-98] - Allow files to be excluded from site generation
* [MSITE-99] - Spanish translation
* [MSITE-105] - No line number for Doxia barfs makes using APT to write
site documentation all but impossible
* [MSITE-80] - refactor site mojo into reusable components
* [MSITE-103] - finish refactoring of category summary pages and index
page report
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
This e-mail, any attachments and the information contained therein (this
message) are confidential and intended solely for the use of the addressee(s). If
you have received this message in error
RE : RE : [vote] Release Maven Site plugin 2.0-beta-5
OK great and thanks.
What about deploy a snapshot ?
I'm not sure but yesterday, I had the following trouble with multi
modules
Root
pom.xml
src/site/site.xml (skin stylus )
module
pom.xml
src/site/site.xml (skin stylus )
others modules with same structure
I have noticed the modules not used the skin.
Question : do I really need to declare the skin in all modules whereas
it's declared in the root site.xml
In previous snapshot version I need to do it.
- Olivier
-Message d'origine-
De : Brett Porter [mailto:[EMAIL PROTECTED]
Envoyé : jeudi 11 mai 2006 09:15
À : Maven Developers List
Objet : Re: RE : [vote] Release Maven Site plugin 2.0-beta-5
I've already fixed this, but unfortunately have not been able to commit
as SVN is still down.
It just needs a null check at the location of the check
Olivier Lamy wrote:
Hi,
Not a maven dev but a user who made some tests ;-).
Today,
I made this :
rm -rf $HOME/.m2/repository/*
mvn -P snapshots -U clean site site:deploy (snapshots profile included
snapshots in apache and codehaus)
I have the stack trace :
[INFO] Generate Dependencies report.
[INFO]
--
--
[ERROR] FATAL ERROR
[INFO]
[INFO] null
[INFO]
[INFO] Trace
java.lang.NullPointerException
at
org.apache.maven.report.projectinfo.ReportResolutionListener$Node.access
$000(ReportResolu
tionListener.java:149)
at
org.apache.maven.report.projectinfo.ReportResolutionListener.manageArtif
act(ReportResolut
ionListener.java:121)
at
org.apache.maven.artifact.resolver.DefaultArtifactCollector.fireEvent(De
faultArtifactColl
ector.java:408)
Glurspp ;-)
In my case it's a multi module site.
The root site is well generated and deployed but failed on the first
module.
Any idea ? (do you need more information on poms or something else ? )
Thanks,
-Olivier
-Message d'origine-
De : Brett Porter [mailto:[EMAIL PROTECTED]
Envoyé : mercredi 10 mai 2006 20:21
À : Maven Developers List
Objet : [vote] Release Maven Site plugin 2.0-beta-5
Hi,
There's a wealth of new features here.
(snapshot pending svn.apache.org coming back up, also I have the docs
here to commit then too)
[ ] +1
[ ] +0
[ ] -1
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11146style
Na
me=Textversion=12541
* [MSITE-23] - problems with site:stage
* [MSITE-24] - Site deployment doesn't allow users in the group to
write
files
* [MSITE-40] - don't generate doc file if it is unchanged
* [MSITE-44] - make site reactor aware
* [MSITE-48] - add reusable skin functionality and create skins
default,
stylus and classic
* [MSITE-51] - add breadcrumbs
* [MSITE-58] - Ability to assign a report to choosen navigation menu
* [MSITE-65] - ${parentProject}\ in default site descriptor doesn't
resolve
* [MSITE-71] - Plugin uses NON interpolated model values (e.g URL) due
to MavenProject.getParent returning non interpolated project
* [MSITE-72] - new non reactor populateModules SiteMojo code assumes
each POM declares its own URL
* [MSITE-73] - new site code fails to generate banner images in
projects
other than site.xml owning project
* [MSITE-74] - Suport proxy
* [MSITE-86] - ${modules} macro placed in site.xml does work properly
* [MSITE-91] - src/site/site.xml hardcoded in AbstractSiteMojo.java
* [MSITE-97] - Site plugin doesn't copy images to target
* [MSITE-102] - SCM files in src/site directory cause 'mvn site' to
fail
- need to exclude files
* [MSITE-104] - There is no way to specify the input encoding of site
documents
* [MSITE-108] - problem with nav generation (collapse = true) snapshot
used 20060315.092459-4.jar (same trouble doxia trunk)
* [MSITE-110] - Use reactor to find parent URL where possible patch
(patch also includes improved calculate relative path and better read
modules from filesystem POM functionality)
* [MSITE-111] - Invalid site-plugin_ja.properties
* [MSITE-113] - generated-site no longer working
* [MSITE-116] - When deploying an individual stage site it goes in the
wrong place
* [MSITE-128] - Site plugin does not properly handle filenames with
more
than one period
* [MSITE-61] - deployment of site descriptor should populate any
modules
items
* [MSITE-62] - make absolute paths relative where possible
* [MSITE-63] - replace interpolated values with decoration model
directives
* [MSITE-94] - Add an image in an item from the site descriptor (m1
style)
* [MSITE-100] - Improve error message about duplicate files
* [MSITE-109] - Site plugin should convert .fml files when working
from
xdocDirectory
* [MSITE-115] - Provide a default value for a staging directory
* [MSITE-127] - Welcome page should work with mvn site:run
*
Re: RE : RE : [vote] Release Maven Site plugin 2.0-beta-5
Yes, sorry - this was down until recently too. I've deployed them both.
Olivier Lamy wrote:
OK great and thanks.
What about deploy a snapshot ?
I'm not sure but yesterday, I had the following trouble with multi
modules
Root
pom.xml
src/site/site.xml (skin stylus )
module
pom.xml
src/site/site.xml (skin stylus )
others modules with same structure
I have noticed the modules not used the skin.
Question : do I really need to declare the skin in all modules whereas
it's declared in the root site.xml
In previous snapshot version I need to do it.
- Olivier
-Message d'origine-
De : Brett Porter [mailto:[EMAIL PROTECTED]
Envoyé : jeudi 11 mai 2006 09:15
À : Maven Developers List
Objet : Re: RE : [vote] Release Maven Site plugin 2.0-beta-5
I've already fixed this, but unfortunately have not been able to commit
as SVN is still down.
It just needs a null check at the location of the check
Olivier Lamy wrote:
Hi,
Not a maven dev but a user who made some tests ;-).
Today,
I made this :
rm -rf $HOME/.m2/repository/*
mvn -P snapshots -U clean site site:deploy (snapshots profile included
snapshots in apache and codehaus)
I have the stack trace :
[INFO] Generate Dependencies report.
[INFO]
--
--
[ERROR] FATAL ERROR
[INFO]
[INFO] null
[INFO]
[INFO] Trace
java.lang.NullPointerException
at
org.apache.maven.report.projectinfo.ReportResolutionListener$Node.access
$000(ReportResolu
tionListener.java:149)
at
org.apache.maven.report.projectinfo.ReportResolutionListener.manageArtif
act(ReportResolut
ionListener.java:121)
at
org.apache.maven.artifact.resolver.DefaultArtifactCollector.fireEvent(De
faultArtifactColl
ector.java:408)
Glurspp ;-)
In my case it's a multi module site.
The root site is well generated and deployed but failed on the first
module.
Any idea ? (do you need more information on poms or something else ? )
Thanks,
-Olivier
-Message d'origine-
De : Brett Porter [mailto:[EMAIL PROTECTED]
Envoyé : mercredi 10 mai 2006 20:21
À : Maven Developers List
Objet : [vote] Release Maven Site plugin 2.0-beta-5
Hi,
There's a wealth of new features here.
(snapshot pending svn.apache.org coming back up, also I have the docs
here to commit then too)
[ ] +1
[ ] +0
[ ] -1
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11146style
Na
me=Textversion=12541
* [MSITE-23] - problems with site:stage
* [MSITE-24] - Site deployment doesn't allow users in the group to
write
files
* [MSITE-40] - don't generate doc file if it is unchanged
* [MSITE-44] - make site reactor aware
* [MSITE-48] - add reusable skin functionality and create skins
default,
stylus and classic
* [MSITE-51] - add breadcrumbs
* [MSITE-58] - Ability to assign a report to choosen navigation menu
* [MSITE-65] - ${parentProject}\ in default site descriptor doesn't
resolve
* [MSITE-71] - Plugin uses NON interpolated model values (e.g URL) due
to MavenProject.getParent returning non interpolated project
* [MSITE-72] - new non reactor populateModules SiteMojo code assumes
each POM declares its own URL
* [MSITE-73] - new site code fails to generate banner images in
projects
other than site.xml owning project
* [MSITE-74] - Suport proxy
* [MSITE-86] - ${modules} macro placed in site.xml does work properly
* [MSITE-91] - src/site/site.xml hardcoded in AbstractSiteMojo.java
* [MSITE-97] - Site plugin doesn't copy images to target
* [MSITE-102] - SCM files in src/site directory cause 'mvn site' to
fail
- need to exclude files
* [MSITE-104] - There is no way to specify the input encoding of site
documents
* [MSITE-108] - problem with nav generation (collapse = true) snapshot
used 20060315.092459-4.jar (same trouble doxia trunk)
* [MSITE-110] - Use reactor to find parent URL where possible patch
(patch also includes improved calculate relative path and better read
modules from filesystem POM functionality)
* [MSITE-111] - Invalid site-plugin_ja.properties
* [MSITE-113] - generated-site no longer working
* [MSITE-116] - When deploying an individual stage site it goes in the
wrong place
* [MSITE-128] - Site plugin does not properly handle filenames with
more
than one period
* [MSITE-61] - deployment of site descriptor should populate any
modules
items
* [MSITE-62] - make absolute paths relative where possible
* [MSITE-63] - replace interpolated values with decoration model
directives
* [MSITE-94] - Add an image in an item from the site descriptor (m1
style)
* [MSITE-100] - Improve error message about duplicate files
* [MSITE-109] - Site plugin should convert .fml files when working
from
xdocDirectory
* [MSITE-115] - Provide a default value for a staging directory
* [MSITE-127] - Welcome page should work with mvn site:run
*
Re: [vote] Release Release plugin 2.0-beta-5
+1 Great work! fabrizio On 5/9/06, Brett Porter [EMAIL PROTECTED] wrote: No, that's not a typo. I'd like to vote to release the release plugin. It has been completely rewritten since you last met it and now has over 250 unit tests covering everything. Nearly all of the JIRA issues have been closed - a select few were deferred to a 2.0 release. I'm working on a small set of docs right now, which I expect will be elaborated on for the 2.0 release. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] release maven-resources-plugin 2.2
+1 fabrizio On 5/9/06, Jesse McConnell [EMAIL PROTECTED] wrote: I would like to call a vote to release the maven-resources-plugin version 2.2 +1 [] 0 [] -1 [] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] Release Maven Project Info Reports 2.0
+1 fabrizio On 5/10/06, Brett Porter [EMAIL PROTECTED] wrote: based on: maven-project-info-reports-plugin 2.0-beta-4-20060510.110344-4 (r405712) This also depends on a release of doxia. [ ] +1 [ ] +0 [ ] -1 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE : RE : RE : [vote] Release Maven Site plugin 2.0-beta-5
Thanks.
But
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] org.apache.maven.doxia.site.decoration.Menu.isInheritAsRef()Z
[INFO]
[INFO] Trace
java.lang.NoSuchMethodError:
org.apache.maven.doxia.site.decoration.Menu.isInheritAsRef()Z
at
org.apache.maven.plugins.site.AbstractSiteMojo.populateModules(AbstractS
iteMojo.java:267)
at
org.apache.maven.plugins.site.AbstractSiteRenderingMojo.getDecorationMod
el(AbstractSiteRe
nderingMojo.java:510)
-Olivier
-Message d'origine-
De : Brett Porter [mailto:[EMAIL PROTECTED]
Envoyé : jeudi 11 mai 2006 09:31
À : Maven Developers List
Objet : Re: RE : RE : [vote] Release Maven Site plugin 2.0-beta-5
Yes, sorry - this was down until recently too. I've deployed them both.
Olivier Lamy wrote:
OK great and thanks.
What about deploy a snapshot ?
I'm not sure but yesterday, I had the following trouble with multi
modules
Root
pom.xml
src/site/site.xml (skin stylus )
module
pom.xml
src/site/site.xml (skin stylus )
others modules with same structure
I have noticed the modules not used the skin.
Question : do I really need to declare the skin in all modules whereas
it's declared in the root site.xml In previous snapshot version I need
to do it.
- Olivier
-Message d'origine-
De : Brett Porter [mailto:[EMAIL PROTECTED]
Envoyé : jeudi 11 mai 2006 09:15
À : Maven Developers List
Objet : Re: RE : [vote] Release Maven Site plugin 2.0-beta-5
I've already fixed this, but unfortunately have not been able to
commit
as SVN is still down.
It just needs a null check at the location of the check
Olivier Lamy wrote:
Hi,
Not a maven dev but a user who made some tests ;-).
Today,
I made this :
rm -rf $HOME/.m2/repository/*
mvn -P snapshots -U clean site site:deploy (snapshots profile
included
snapshots in apache and codehaus)
I have the stack trace :
[INFO] Generate Dependencies report.
[INFO]
-
-
--
[ERROR] FATAL ERROR
[INFO]
--
--
[INFO] null
[INFO]
--
--
[INFO] Trace
java.lang.NullPointerException
at
org.apache.maven.report.projectinfo.ReportResolutionListener$Node.acce
ss
$000(ReportResolu
tionListener.java:149)
at
org.apache.maven.report.projectinfo.ReportResolutionListener.manageArt
if
act(ReportResolut
ionListener.java:121)
at
org.apache.maven.artifact.resolver.DefaultArtifactCollector.fireEvent(
De
faultArtifactColl
ector.java:408)
Glurspp ;-)
In my case it's a multi module site.
The root site is well generated and deployed but failed on the first
module.
Any idea ? (do you need more information on poms or something else ?
)
Thanks,
-Olivier
-Message d'origine-
De : Brett Porter [mailto:[EMAIL PROTECTED]
Envoyé : mercredi 10 mai 2006 20:21
À : Maven Developers List
Objet : [vote] Release Maven Site plugin 2.0-beta-5
Hi,
There's a wealth of new features here.
(snapshot pending svn.apache.org coming back up, also I have the docs
here to commit then too)
[ ] +1
[ ] +0
[ ] -1
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11146styl
e
Na
me=Textversion=12541
* [MSITE-23] - problems with site:stage
* [MSITE-24] - Site deployment doesn't allow users in the group to
write
files
* [MSITE-40] - don't generate doc file if it is unchanged
* [MSITE-44] - make site reactor aware
* [MSITE-48] - add reusable skin functionality and create skins
default,
stylus and classic
* [MSITE-51] - add breadcrumbs
* [MSITE-58] - Ability to assign a report to choosen navigation menu
* [MSITE-65] - ${parentProject}\ in default site descriptor doesn't
resolve
* [MSITE-71] - Plugin uses NON interpolated model values (e.g URL)
due
to MavenProject.getParent returning non interpolated project
* [MSITE-72] - new non reactor populateModules SiteMojo code assumes
each POM declares its own URL
* [MSITE-73] - new site code fails to generate banner images in
projects
other than site.xml owning project
* [MSITE-74] - Suport proxy
* [MSITE-86] - ${modules} macro placed in site.xml does work properly
* [MSITE-91] - src/site/site.xml hardcoded in AbstractSiteMojo.java
* [MSITE-97] - Site plugin doesn't copy images to target
* [MSITE-102] - SCM files in src/site directory cause 'mvn site' to
fail
- need to exclude files
* [MSITE-104] - There is no way to specify the input encoding of site
documents
* [MSITE-108] - problem with nav generation (collapse = true)
snapshot
used 20060315.092459-4.jar (same trouble doxia trunk)
* [MSITE-110] - Use reactor
Re: RE : RE : RE : [vote] Release Maven Site plugin 2.0-beta-5
Sorry, forgot to deploy that one. Try now.
- Brett
Olivier Lamy wrote:
Thanks.
But
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] org.apache.maven.doxia.site.decoration.Menu.isInheritAsRef()Z
[INFO]
[INFO] Trace
java.lang.NoSuchMethodError:
org.apache.maven.doxia.site.decoration.Menu.isInheritAsRef()Z
at
org.apache.maven.plugins.site.AbstractSiteMojo.populateModules(AbstractS
iteMojo.java:267)
at
org.apache.maven.plugins.site.AbstractSiteRenderingMojo.getDecorationMod
el(AbstractSiteRe
nderingMojo.java:510)
-Olivier
-Message d'origine-
De : Brett Porter [mailto:[EMAIL PROTECTED]
Envoyé : jeudi 11 mai 2006 09:31
À : Maven Developers List
Objet : Re: RE : RE : [vote] Release Maven Site plugin 2.0-beta-5
Yes, sorry - this was down until recently too. I've deployed them both.
Olivier Lamy wrote:
OK great and thanks.
What about deploy a snapshot ?
I'm not sure but yesterday, I had the following trouble with multi
modules
Root
pom.xml
src/site/site.xml (skin stylus )
module
pom.xml
src/site/site.xml (skin stylus )
others modules with same structure
I have noticed the modules not used the skin.
Question : do I really need to declare the skin in all modules whereas
it's declared in the root site.xml In previous snapshot version I need
to do it.
- Olivier
-Message d'origine-
De : Brett Porter [mailto:[EMAIL PROTECTED]
Envoyé : jeudi 11 mai 2006 09:15
À : Maven Developers List
Objet : Re: RE : [vote] Release Maven Site plugin 2.0-beta-5
I've already fixed this, but unfortunately have not been able to
commit
as SVN is still down.
It just needs a null check at the location of the check
Olivier Lamy wrote:
Hi,
Not a maven dev but a user who made some tests ;-).
Today,
I made this :
rm -rf $HOME/.m2/repository/*
mvn -P snapshots -U clean site site:deploy (snapshots profile
included
snapshots in apache and codehaus)
I have the stack trace :
[INFO] Generate Dependencies report.
[INFO]
-
-
--
[ERROR] FATAL ERROR
[INFO]
--
--
[INFO] null
[INFO]
--
--
[INFO] Trace
java.lang.NullPointerException
at
org.apache.maven.report.projectinfo.ReportResolutionListener$Node.acce
ss
$000(ReportResolu
tionListener.java:149)
at
org.apache.maven.report.projectinfo.ReportResolutionListener.manageArt
if
act(ReportResolut
ionListener.java:121)
at
org.apache.maven.artifact.resolver.DefaultArtifactCollector.fireEvent(
De
faultArtifactColl
ector.java:408)
Glurspp ;-)
In my case it's a multi module site.
The root site is well generated and deployed but failed on the first
module.
Any idea ? (do you need more information on poms or something else ?
)
Thanks,
-Olivier
-Message d'origine-
De : Brett Porter [mailto:[EMAIL PROTECTED]
Envoyé : mercredi 10 mai 2006 20:21
À : Maven Developers List
Objet : [vote] Release Maven Site plugin 2.0-beta-5
Hi,
There's a wealth of new features here.
(snapshot pending svn.apache.org coming back up, also I have the docs
here to commit then too)
[ ] +1
[ ] +0
[ ] -1
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11146styl
e
Na
me=Textversion=12541
* [MSITE-23] - problems with site:stage
* [MSITE-24] - Site deployment doesn't allow users in the group to
write
files
* [MSITE-40] - don't generate doc file if it is unchanged
* [MSITE-44] - make site reactor aware
* [MSITE-48] - add reusable skin functionality and create skins
default,
stylus and classic
* [MSITE-51] - add breadcrumbs
* [MSITE-58] - Ability to assign a report to choosen navigation menu
* [MSITE-65] - ${parentProject}\ in default site descriptor doesn't
resolve
* [MSITE-71] - Plugin uses NON interpolated model values (e.g URL)
due
to MavenProject.getParent returning non interpolated project
* [MSITE-72] - new non reactor populateModules SiteMojo code assumes
each POM declares its own URL
* [MSITE-73] - new site code fails to generate banner images in
projects
other than site.xml owning project
* [MSITE-74] - Suport proxy
* [MSITE-86] - ${modules} macro placed in site.xml does work properly
* [MSITE-91] - src/site/site.xml hardcoded in AbstractSiteMojo.java
* [MSITE-97] - Site plugin doesn't copy images to target
* [MSITE-102] - SCM files in src/site directory cause 'mvn site' to
fail
- need to exclude files
* [MSITE-104] - There is no way to specify the input encoding of site
documents
* [MSITE-108] - problem with nav generation (collapse = true)
snapshot
used 20060315.092459-4.jar (same trouble doxia trunk)
* [MSITE-110] - Use reactor to find parent URL where
RE : RE : RE : RE : [vote] Release Maven Site plugin 2.0-beta-5
Great and big thanks. Works great.
I can add my user vote : 99E+10 ;-))
-Olivier
-Message d'origine-
De : Brett Porter [mailto:[EMAIL PROTECTED]
Envoyé : jeudi 11 mai 2006 10:42
À : Maven Developers List
Objet : Re: RE : RE : RE : [vote] Release Maven Site plugin 2.0-beta-5
Sorry, forgot to deploy that one. Try now.
- Brett
Olivier Lamy wrote:
Thanks.
But
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] org.apache.maven.doxia.site.decoration.Menu.isInheritAsRef()Z
[INFO]
[INFO] Trace
java.lang.NoSuchMethodError:
org.apache.maven.doxia.site.decoration.Menu.isInheritAsRef()Z
at
org.apache.maven.plugins.site.AbstractSiteMojo.populateModules(AbstractS
iteMojo.java:267)
at
org.apache.maven.plugins.site.AbstractSiteRenderingMojo.getDecorationMod
el(AbstractSiteRe
nderingMojo.java:510)
-Olivier
-Message d'origine-
De : Brett Porter [mailto:[EMAIL PROTECTED]
Envoyé : jeudi 11 mai 2006 09:31
À : Maven Developers List
Objet : Re: RE : RE : [vote] Release Maven Site plugin 2.0-beta-5
Yes, sorry - this was down until recently too. I've deployed them
both.
Olivier Lamy wrote:
OK great and thanks.
What about deploy a snapshot ?
I'm not sure but yesterday, I had the following trouble with multi
modules
Root
pom.xml
src/site/site.xml (skin stylus )
module
pom.xml
src/site/site.xml (skin stylus )
others modules with same structure
I have noticed the modules not used the skin.
Question : do I really need to declare the skin in all modules
whereas
it's declared in the root site.xml In previous snapshot version I
need
to do it.
- Olivier
-Message d'origine-
De : Brett Porter [mailto:[EMAIL PROTECTED]
Envoyé : jeudi 11 mai 2006 09:15
À : Maven Developers List
Objet : Re: RE : [vote] Release Maven Site plugin 2.0-beta-5
I've already fixed this, but unfortunately have not been able to
commit
as SVN is still down.
It just needs a null check at the location of the check
Olivier Lamy wrote:
Hi,
Not a maven dev but a user who made some tests ;-).
Today,
I made this :
rm -rf $HOME/.m2/repository/*
mvn -P snapshots -U clean site site:deploy (snapshots profile
included
snapshots in apache and codehaus)
I have the stack trace :
[INFO] Generate Dependencies report.
[INFO]
-
-
--
[ERROR] FATAL ERROR
[INFO]
-
-
--
[INFO] null
[INFO]
-
-
--
[INFO] Trace
java.lang.NullPointerException
at
org.apache.maven.report.projectinfo.ReportResolutionListener$Node.acc
e
ss
$000(ReportResolu
tionListener.java:149)
at
org.apache.maven.report.projectinfo.ReportResolutionListener.manageAr
t
if
act(ReportResolut
ionListener.java:121)
at
org.apache.maven.artifact.resolver.DefaultArtifactCollector.fireEvent
(
De
faultArtifactColl
ector.java:408)
Glurspp ;-)
In my case it's a multi module site.
The root site is well generated and deployed but failed on the first
module.
Any idea ? (do you need more information on poms or something else ?
)
Thanks,
-Olivier
-Message d'origine-
De : Brett Porter [mailto:[EMAIL PROTECTED]
Envoyé : mercredi 10 mai 2006 20:21
À : Maven Developers List
Objet : [vote] Release Maven Site plugin 2.0-beta-5
Hi,
There's a wealth of new features here.
(snapshot pending svn.apache.org coming back up, also I have the
docs
here to commit then too)
[ ] +1
[ ] +0
[ ] -1
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11146sty
l
e
Na
me=Textversion=12541
* [MSITE-23] - problems with site:stage
* [MSITE-24] - Site deployment doesn't allow users in the group to
write
files
* [MSITE-40] - don't generate doc file if it is unchanged
* [MSITE-44] - make site reactor aware
* [MSITE-48] - add reusable skin functionality and create skins
default,
stylus and classic
* [MSITE-51] - add breadcrumbs
* [MSITE-58] - Ability to assign a report to choosen navigation menu
* [MSITE-65] - ${parentProject}\ in default site descriptor doesn't
resolve
* [MSITE-71] - Plugin uses NON interpolated model values (e.g URL)
due
to MavenProject.getParent returning non interpolated project
* [MSITE-72] - new non reactor populateModules SiteMojo code assumes
each POM declares its own URL
* [MSITE-73] - new site code fails to generate banner images in
projects
other than site.xml owning project
* [MSITE-74] - Suport proxy
* [MSITE-86] - ${modules} macro placed in site.xml does work
properly
* [MSITE-91] - src/site/site.xml hardcoded in
Re: [vote] Release Maven Project Info Reports 2.0
+1 (user) Fabrizio Giustina wrote: +1 fabrizio On 5/10/06, Brett Porter [EMAIL PROTECTED] wrote: based on: maven-project-info-reports-plugin 2.0-beta-4-20060510.110344-4 (r405712) This also depends on a release of doxia. [ ] +1 [ ] +0 [ ] -1 -- With kind regards, Geoffrey De Smet - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
I have a problem executing the maven-release-plugin
I have copied the maven-release-plugin jar into maven2/lib now I want to execute mvn release:prepare In the component, I want to release, I declared build plugins plugin groupIdmaven/groupId artifactIdmaven--release-plugin/artifactId version1.4/version But I get a Build Error: maven-release.plugin does not exit or no valid version could be found. What is the problem ? -- View this message in context: http://www.nabble.com/I-have-a-problem-executing-the-maven-release-plugin-t1600159.html#a4339090 Sent from the Maven - Dev forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: I have a problem executing the maven-release-plugin
it's maven-release-plugin and not maven--release-plugin Emmanuel mathapfahl a écrit : I have copied the maven-release-plugin jar into maven2/lib now I want to execute mvn release:prepare In the component, I want to release, I declared build plugins plugin groupIdmaven/groupId artifactIdmaven--release-plugin/artifactId version1.4/version But I get a Build Error: maven-release.plugin does not exit or no valid version could be found. What is the problem ? -- View this message in context: http://www.nabble.com/I-have-a-problem-executing-the-maven-release-plugin-t1600159.html#a4339090 Sent from the Maven - Dev forum at Nabble.com. - 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: I have a problem executing the maven-release-plugin
thanks but this wasn't the problem ! -- View this message in context: http://www.nabble.com/I-have-a-problem-executing-the-maven-release-plugin-t1600159.html#a4339495 Sent from the Maven - Dev forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: I have a problem executing the maven-release-plugin
Emmanuel Venisse wrote: it's maven-release-plugin and not maven--release-plugin and: - it's org.apache.maven.plugins for the group - the version is 2.0-beta-3 - you don't need to put it in $M2_HOME/lib These questions should be asked of [EMAIL PROTECTED] - Brett Emmanuel mathapfahl a écrit : I have copied the maven-release-plugin jar into maven2/lib now I want to execute mvn release:prepare In the component, I want to release, I declared build plugins plugin groupIdmaven/groupId artifactIdmaven--release-plugin/artifactId version1.4/version But I get a Build Error: maven-release.plugin does not exit or no valid version could be found. What is the problem ? -- View this message in context: http://www.nabble.com/I-have-a-problem-executing-the-maven-release-plugin-t1600159.html#a4339090 Sent from the Maven - Dev forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: I have a problem executing the maven-release-plugin
you don't need to copy it in maven2/lib, the lib directory is for maven core lib. All plugins are downloaded by maven when it's necessary. The groupId is org.apache.maven.plugins instead of maven and the version 1.4 doesn't exist, the latest is 2.0-beta-3, in few days, 2.0-beta-4 will be available Emmanuel Emmanuel Venisse a écrit : it's maven-release-plugin and not maven--release-plugin Emmanuel mathapfahl a écrit : I have copied the maven-release-plugin jar into maven2/lib now I want to execute mvn release:prepare In the component, I want to release, I declared build plugins plugin groupIdmaven/groupId artifactIdmaven--release-plugin/artifactId version1.4/version But I get a Build Error: maven-release.plugin does not exit or no valid version could be found. What is the problem ? -- View this message in context: http://www.nabble.com/I-have-a-problem-executing-the-maven-release-plugin-t1600159.html#a4339090 Sent from the Maven - Dev forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Maven Home
How do you get the home directory for a maven project? Not where maven is
installed but where main maven.xml, target, project.properties, etc. is
stored.
I've tried ${basedir} but this gives the base directory for each project,
--main_project
---folder1
---maven.xml, etc
---folder2
---maven.xml, etc
---folder3
---maven.xml, etc
---target
--- ...
---maven.xml
---project.properties
So I need to get the main_project/target folder by specifying one of the ${}
parameters.
Any ideas? Thanks.
--
View this message in context:
http://www.nabble.com/Maven-Home-t1600432.html#a4339843
Sent from the Maven - Dev forum at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Nabble
I'm noticing a vast increase in the amount of user questions coming in to this list from Nabble. The noise doesn't particularly concern me and I can certainly delete them, but I think it's a problem because it'll keep going up and will probably leave more questions unanswered. Anyone have any suggestions? I've not really used it. - Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Nabble
Why do you want to delete them? users use Nabble forum functionality instead of sending directly a mail to our lists but the result is the same, all messages come in our lists. Emmanuel Brett Porter a écrit : I'm noticing a vast increase in the amount of user questions coming in to this list from Nabble. The noise doesn't particularly concern me and I can certainly delete them, but I think it's a problem because it'll keep going up and will probably leave more questions unanswered. Anyone have any suggestions? I've not really used it. - Brett - 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: I have a problem executing the maven-release-plugin
Thanks You are right. groupId and version weren't correct. But at www.ibilio.org/maven2/maven/maven-release-plugin there is a version 1.4 with a groupId maven. I don't understand this. -- View this message in context: http://www.nabble.com/I-have-a-problem-executing-the-maven-release-plugin-t1600159.html#a4340373 Sent from the Maven - Dev forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Nabble
On that note, is there a way to obfuscate our email addresses for these forums? I've noticed a huge increase in spam since I started posting on the apache lists. Many other lists remove the email address so that bots can't pick them up. -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: Thursday, May 11, 2006 9:25 AM To: Maven Developers List Subject: Re: Nabble Why do you want to delete them? users use Nabble forum functionality instead of sending directly a mail to our lists but the result is the same, all messages come in our lists. Emmanuel Brett Porter a écrit : I'm noticing a vast increase in the amount of user questions coming in to this list from Nabble. The noise doesn't particularly concern me and I can certainly delete them, but I think it's a problem because it'll keep going up and will probably leave more questions unanswered. Anyone have any suggestions? I've not really used it. - Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Nabble
Emmanuel Venisse wrote: Why do you want to delete them? I just mean from my dev folder. users use Nabble forum functionality instead of sending directly a mail to our lists but the result is the same, all messages come in our lists. right - just the wrong list :) - Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Nabble
Just like on gmane (newsgroups of mailing lists) there are 2 separate lists(forums on nabble): users and dev. User shouldn't ask user questions on the dev list. Brett Porter wrote: Emmanuel Venisse wrote: Why do you want to delete them? I just mean from my dev folder. users use Nabble forum functionality instead of sending directly a mail to our lists but the result is the same, all messages come in our lists. right - just the wrong list :) - Brett -- With kind regards, Geoffrey De Smet - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Nabble
I wonder if there is a way to ask Nabble to deny submitting a new email directly to dev@ list from their interface, but still allow reading etc, and of course allow email to [EMAIL PROTECTED] I'd also like to make sure that the Maven website provides proper guidance for visitors as to which email address to send their problem to. Nearly all emails should go to [EMAIL PROTECTED] And yet we get them here in dev@ frequently, then today we got one at issues@, etc. This is *not* entirely clear to someone who is visiting the Maven website for the first time: http://maven.apache.org/mail-lists.html Perhaps we need a description tag in the mailingList element? Wayne On 5/11/06, Geoffrey De Smet [EMAIL PROTECTED] wrote: Just like on gmane (newsgroups of mailing lists) there are 2 separate lists(forums on nabble): users and dev. User shouldn't ask user questions on the dev list. Brett Porter wrote: Emmanuel Venisse wrote: Why do you want to delete them? I just mean from my dev folder. users use Nabble forum functionality instead of sending directly a mail to our lists but the result is the same, all messages come in our lists. right - just the wrong list :) - Brett -- With kind regards, Geoffrey De Smet - 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]
commits and releases
Hi, In case you don't notice, we don't currently have commit access to the Apache Subversion repository as it is undergoing some extended maintenance. It could be hours, or a week. I've gone through and setup a line of patches for a bunch of JIRA issues. I will take care of committing them when SVN comes back (it may be next week) and will continue with the releases after that. I've closed the respective issues and attached patches there for those needing to try them. Snapshots should still be up to date. Please continue voting, however I won't be modifying the releases from their current state unless there is a real blocker. The releases are: doxia-1.0-alpha-8 maven-assembly-plugin-2.1 maven-checkstyle-plugin-2.1 maven-idea-plugin-2.0 maven-javadoc-plugin-2.0 maven-jxr-plugin-2.0 maven-pmd-plugin-2.0 maven-project-info-reports-plugin-2.0 maven-release-plugin-2.0-beta-4 maven-resources-plugin-2.2 maven-site-plugin-2.0-beta-5 maven-surefire-plugin-2.2 maven-war-plugin-2.0 surefire-2.0 wagon-webdav-1.0-beta-1 Cheers, Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: commits and releases
On 5/11/06, Brett Porter [EMAIL PROTECTED] wrote: Hi, In case you don't notice, we don't currently have commit access to the Apache Subversion repository as it is undergoing some extended maintenance. It could be hours, or a week. I've gone through and setup a line of patches for a bunch of JIRA issues. I will take care of committing them when SVN comes back (it may be next week) and will continue with the releases after that. I've closed the respective issues and attached patches there for those needing to try them. Snapshots should still be up to date. since svn.apache.org is down, could you deploy the snapshots at codehaus? Please continue voting, however I won't be modifying the releases from their current state unless there is a real blocker. The releases are: doxia-1.0-alpha-8 maven-assembly-plugin-2.1 maven-checkstyle-plugin-2.1 maven-idea-plugin-2.0 maven-javadoc-plugin-2.0 maven-jxr-plugin-2.0 maven-pmd-plugin-2.0 maven-project-info-reports-plugin-2.0 maven-release-plugin-2.0-beta-4 maven-resources-plugin-2.2 maven-site-plugin-2.0-beta-5 maven-surefire-plugin-2.2 maven-war-plugin-2.0 surefire-2.0 wagon-webdav-1.0-beta-1 Cheers, Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: commits and releases
dan tran wrote: since svn.apache.org is down, could you deploy the snapshots at codehaus? It was up. I believe they are doing some more maintenance right now, but it will be back (in read only mode) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Nabble
One problem is that the descriptions on the Maven web site are not present on Nabble. So to someone who is just searching the mailing lists has no knowledge of what the various lists are. My pet peeve is that most messages from Nabble do not have the previous messages in the thread so it is a little difficult to know what the reply is in reference to. -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Thursday, May 11, 2006 11:02 To: Maven Developers List Subject: Re: Nabble I wonder if there is a way to ask Nabble to deny submitting a new email directly to dev@ list from their interface, but still allow reading etc, and of course allow email to [EMAIL PROTECTED] I'd also like to make sure that the Maven website provides proper guidance for visitors as to which email address to send their problem to. Nearly all emails should go to [EMAIL PROTECTED] And yet we get them here in dev@ frequently, then today we got one at issues@, etc. This is *not* entirely clear to someone who is visiting the Maven website for the first time: http://maven.apache.org/mail-lists.html Perhaps we need a description tag in the mailingList element? Wayne On 5/11/06, Geoffrey De Smet [EMAIL PROTECTED] wrote: Just like on gmane (newsgroups of mailing lists) there are 2 separate lists(forums on nabble): users and dev. User shouldn't ask user questions on the dev list. Brett Porter wrote: Emmanuel Venisse wrote: Why do you want to delete them? I just mean from my dev folder. users use Nabble forum functionality instead of sending directly a mail to our lists but the result is the same, all messages come in our lists. right - just the wrong list :) - Brett -- With kind regards, Geoffrey De Smet - 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] This communication is the property of Qwest and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [jira] Commented: (MDEP-2) Sibling Dependency Not Included in copy-dependencies output during multi-project build
I think we should stop any work in dependency-maven-plugin and move forward to a new release of maven-dependency-plugin. +1 to remove it from codehaus. -D On 5/11/06, Brian Fox (JIRA) [EMAIL PROTECTED] wrote: [ http://jira.codehaus.org/browse/MDEP-2?page=comments#action_65209 ] Brian Fox commented on MDEP-2: -- The version in maven repo represents 2.x where I started a complete refactor. I left the source here in mojo for now since it is essentially the same as 1.0 that has been released. Sibling Dependency Not Included in copy-dependencies output during multi-project build -- Key: MDEP-2 URL: http://jira.codehaus.org/browse/MDEP-2 Project: Maven 2.x Dependency Plugin Type: Bug Reporter: Stephen Duncan Jr Assignee: Kenney Westerhof Fix For: 1.1 Attachments: dependency-test.zip Using the following structure dependency-test - module1 - module2 I have the dependency-maven-plugin:copy-dependencies goal attached the package phase of the module2 module. module2 has a dependency on module1. When I run mvn package from the module2 folder, it correctly includes the module1 jar in the target/dependency folder. When I run mvn package from the dependency-test folder, the module1 jar is not included in the impl/target/dependency folder. A simple example of the problem is attached. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [jira] Commented: (MDEP-2) Sibling Dependency Not Included in copy-dependencies output during multi-project build
On Thu, 11 May 2006, dan tran wrote: +1, it's confusing :) I think we should stop any work in dependency-maven-plugin and move forward to a new release of maven-dependency-plugin. +1 to remove it from codehaus. -D On 5/11/06, Brian Fox (JIRA) [EMAIL PROTECTED] wrote: [ http://jira.codehaus.org/browse/MDEP-2?page=comments#action_65209 ] Brian Fox commented on MDEP-2: -- The version in maven repo represents 2.x where I started a complete refactor. I left the source here in mojo for now since it is essentially the same as 1.0 that has been released. Sibling Dependency Not Included in copy-dependencies output during multi-project build -- Key: MDEP-2 URL: http://jira.codehaus.org/browse/MDEP-2 Project: Maven 2.x Dependency Plugin Type: Bug Reporter: Stephen Duncan Jr Assignee: Kenney Westerhof Fix For: 1.1 Attachments: dependency-test.zip Using the following structure dependency-test - module1 - module2 I have the dependency-maven-plugin:copy-dependencies goal attached the package phase of the module2 module. module2 has a dependency on module1. When I run mvn package from the module2 folder, it correctly includes the module1 jar in the target/dependency folder. When I run mvn package from the dependency-test folder, the module1 jar is not included in the impl/target/dependency folder. A simple example of the problem is attached. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Kenney Westerhof http://www.neonics.com GPG public key: http://www.gods.nl/~forge/kenneyw.key - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Sun Jars Maven repository hosted by Sun is now available
Hi everyone, I noticed that Sun now has a Maven repository that hosts their jars that have been such a hassle to install the first time Maven 2 gets going. The java.net webpage for the Maven repository project is at https://maven-repository.dev.java.net/ The repository is located at https://maven-repository.dev.java.net/nonav/repository/ It might be worthwhile to add the repository to the default Maven 2 configuration so new users will have a better experience getting going with Maven 2. In the meantime, it might be handy to post how to add the repository to their config file on the Coping with Sun Jars page. Hope this helps, Jim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Sun Jars Maven repository hosted by Sun is now available
We're actually working with them to clean up the information in there and automatically sync them to the main mirror. Unfortunately, since it's a M1 repository, there is no transitive dependency information in there (not a big deal for most, but would be handy for some of the newer ones that have multiple artifacts). - Brett Jim Bethancourt wrote: Hi everyone, I noticed that Sun now has a Maven repository that hosts their jars that have been such a hassle to install the first time Maven 2 gets going. The java.net webpage for the Maven repository project is at https://maven-repository.dev.java.net/ The repository is located at https://maven-repository.dev.java.net/nonav/repository/ It might be worthwhile to add the repository to the default Maven 2 configuration so new users will have a better experience getting going with Maven 2. In the meantime, it might be handy to post how to add the repository to their config file on the Coping with Sun Jars page. Hope this helps, Jim - 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: Sun Jars Maven repository hosted by Sun is now available
Jim Bethancourt wrote: Hi everyone, I noticed that Sun now has a Maven repository that hosts their jars that have been such a hassle to install the first time Maven 2 gets going. The java.net webpage for the Maven repository project is at https://maven-repository.dev.java.net/ The repository is located at https://maven-repository.dev.java.net/nonav/repository/ It might be worthwhile to add the repository to the default Maven 2 configuration so new users will have a better experience getting going with Maven 2. In the meantime, it might be handy to post how to add the repository to their config file on the Coping with Sun Jars page. H this looks like a M1 repo to me. Am I mistaken? Alex - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Sun Jars Maven repository hosted by Sun is now available
Thanks for the quick response and rundown of the situation. I had just noticed it and was unsure if the Maven team had come across it. Best of luck with the clean up. :-) Cheers, Jim On 5/11/06, Brett Porter [EMAIL PROTECTED] wrote: We're actually working with them to clean up the information in there and automatically sync them to the main mirror. Unfortunately, since it's a M1 repository, there is no transitive dependency information in there (not a big deal for most, but would be handy for some of the newer ones that have multiple artifacts). - Brett Jim Bethancourt wrote: Hi everyone, I noticed that Sun now has a Maven repository that hosts their jars that have been such a hassle to install the first time Maven 2 gets going. The java.net webpage for the Maven repository project is at https://maven-repository.dev.java.net/ The repository is located at https://maven-repository.dev.java.net/nonav/repository/ It might be worthwhile to add the repository to the default Maven 2 configuration so new users will have a better experience getting going with Maven 2. In the meantime, it might be handy to post how to add the repository to their config file on the Coping with Sun Jars page. Hope this helps, Jim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Sun Jars Maven repository hosted by Sun is now available
On May 11, 2006, at 11:44 AM, Alex Karasulu wrote: H this looks like a M1 repo to me. Am I mistaken? Looks like that to me too, and they are missing a fair number of jars. -b - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] [m1] plugin releases : ant pdf
On 5/9/06, Lukas Theussl [EMAIL PROTECTED] wrote: +1 x2 Just some comments on the ant plugin: * there is a layout problem in the table of the properties page (maven.ant.excludeTests) Fixed, Thx. * there is an issue with m1.0 compatibility: running maven genapp - ant - ant:execute fails on m1.0.2 because junit classes cannot be found. I suppose it's because the build file is ant-1.6 compatible, but putting maven.ant.compatibility=1.5 does not solve the problem. No it's not due to ant 1.5/1.6. I can also reproduce this problem with maven 1.1. The tests are activated because ant finds in the maven's classloader the junit classes. But junit isn't in the project dependencies (this dependency is automatically added by the test plugin) thus the compilation fails. I'll add a note on the execute goal to explain that the result can differ between the real ant application and this goal. * The maven.ant.compatibility property is not documented. Fixed, Thx. I don't know if the second point can be fixed easily, but it shouldn't hold off the release (just document it!). Thanks, -Lukas I redeployed the web site I'll commit these changes ASAP Arnaud
Re: Sun Jars Maven repository hosted by Sun is now available
Yes, its a M1 repo. This is not a big deal for M2, as you can access M1 repos from M2 using the layoutlegacy/layout element. Wayne On 5/11/06, Brian Topping [EMAIL PROTECTED] wrote: On May 11, 2006, at 11:44 AM, Alex Karasulu wrote: H this looks like a M1 repo to me. Am I mistaken? Looks like that to me too, and they are missing a fair number of jars. -b - 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] Subscription: Design Best Practices
Issue Subscription Filter: Design Best Practices (34 issues) Subscriber: mavendevlist Key Summary MNG-612 implement conflict resolution techniques http://jira.codehaus.org/browse/MNG-612 MNG-1508Need a process-test-classes phase http://jira.codehaus.org/browse/MNG-1508 MNG-1381best practices: testing strategies http://jira.codehaus.org/browse/MNG-1381 MNG-1936pattern: for mojo parameters which have default values in the POM we need standard usage http://jira.codehaus.org/browse/MNG-1936 MNG-1563how to write integration tests http://jira.codehaus.org/browse/MNG-1563 MNG-474 performance improvement for forked lifecycles http://jira.codehaus.org/browse/MNG-474 MNG-2125[doc] when and how to define plugins in a pom http://jira.codehaus.org/browse/MNG-2125 MNG-1950Ability to introduce new lifecycles phases http://jira.codehaus.org/browse/MNG-1950 MNG-2129generated source repo page is misleading when added to the general site. http://jira.codehaus.org/browse/MNG-2129 MNG-1305Document Maven's own development process http://jira.codehaus.org/browse/MNG-1305 MNG-1931add a reportingManagement section http://jira.codehaus.org/browse/MNG-1931 MNG-1463best practices: plugin inheritance for a multi project build http://jira.codehaus.org/browse/MNG-1463 MNG-1437How to make additions to the POM and have it be backward/forward compatible http://jira.codehaus.org/browse/MNG-1437 MNG-1867deprecate system scope, analyse other use cases http://jira.codehaus.org/browse/MNG-1867 MNG-1468best practices: version management in multi project builds http://jira.codehaus.org/browse/MNG-1468 MNG-1452best practices: deployment of aggregate JARs produced by the assembly plug-in http://jira.codehaus.org/browse/MNG-1452 MNG-1885Uniquely identify modules by module name and version number http://jira.codehaus.org/browse/MNG-1885 MNG-416 best practices: multiple profile deployments http://jira.codehaus.org/browse/MNG-416 MNG-1441Starting thinking about a proper distributed repository mechanism a la CPAN http://jira.codehaus.org/browse/MNG-1441 MNG-367 best practices: multi-user installation http://jira.codehaus.org/browse/MNG-367 MNG-140 refactor maven-artifact http://jira.codehaus.org/browse/MNG-140 MNG-1425best practices: the location of configuration files vs resources http://jira.codehaus.org/browse/MNG-1425 MNG-41 best practices: site management http://jira.codehaus.org/browse/MNG-41 MNG-139 server definitions should be reusable http://jira.codehaus.org/browse/MNG-139 MNG-1440Developer Object Model (DOM) http://jira.codehaus.org/browse/MNG-1440 MNG-657 possible chicken and egg problem with extensions http://jira.codehaus.org/browse/MNG-657 MNG-125 guarded mojo execution http://jira.codehaus.org/browse/MNG-125 MNG-1439Organization Object Model (OOM) http://jira.codehaus.org/browse/MNG-1439 MNG-905 review clean repo install of m2 for download trimming http://jira.codehaus.org/browse/MNG-905 MNG-1423best practices: setting up multi-module build http://jira.codehaus.org/browse/MNG-1423 MNG-1569Make build process info read-only to mojos, and provide mechanism for explicit out-params for mojos to declare http://jira.codehaus.org/browse/MNG-1569 MNG-647 Allow Maven 2 to be monitored using JMX. http://jira.codehaus.org/browse/MNG-647 MNG-868 Use uniform format for properties and other tags http://jira.codehaus.org/browse/MNG-868 MNG-939 specify maven settings from command line http://jira.codehaus.org/browse/MNG-939 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Sun Jars Maven repository hosted by Sun is now available
That repo is pretty messy still and has no m2 poms. I suggest everybody that if they want something from there open a upload request to move it over to ibiblio. On 5/11/06, Wayne Fay [EMAIL PROTECTED] wrote: Yes, its a M1 repo. This is not a big deal for M2, as you can access M1 repos from M2 using the layoutlegacy/layout element. Wayne On 5/11/06, Brian Topping [EMAIL PROTECTED] wrote: On May 11, 2006, at 11:44 AM, Alex Karasulu wrote: H this looks like a M1 repo to me. Am I mistaken? Looks like that to me too, and they are missing a fair number of jars. -b - 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] -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
