[jira] Work started: (WAGON-101) Allow use of streams for get, getIfNewer and put
[ http://jira.codehaus.org/browse/WAGON-101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on WAGON-101 started by Brett Porter. > Allow use of streams for get, getIfNewer and put > > > Key: WAGON-101 > URL: http://jira.codehaus.org/browse/WAGON-101 > Project: Maven Wagon > Issue Type: New Feature > Components: wagon-provider-api >Affects Versions: 1.0-beta-3 >Reporter: James William Dumay >Assignee: Brett Porter > Fix For: 1.0-beta-3 > > Attachments: wagon-streaming.patch > > > Allow the use of Streams with get, getIfNewer and put. -- 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
[jira] Created: (MNG-3609) xbean breaks embedding within netbeans by using java.beans.PropertyEditorManager.registerEditor
xbean breaks embedding within netbeans by using java.beans.PropertyEditorManager.registerEditor --- Key: MNG-3609 URL: http://jira.codehaus.org/browse/MNG-3609 Project: Maven 2 Issue Type: Bug Components: Embedding Affects Versions: 2.1 Environment: netbeans 6.1, mevenide 3.1.2+ Reporter: Milos Kleint Attachments: xbean.patch The xbean binary shipping with maven in 2.1 is registering PropertyEditors via java.beans.PropertyEditorManager.registerEditor() that's wracking havoc in the IDE's own code that relies on it's own property editors with customizer ui to be present. http://www.netbeans.org/issues/show_bug.cgi?id=135868 is the obvious error everyone noticed, there's more subtle ones as well, like being unable to edit properties, or broken form GUI editor that's not processing real numbers correctly. I've hotfixed the issue by commenting out the property editor registration in xbean (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
[jira] Closed: (WAGON-215) sftp is much slower than scp for equivalent requests
[ http://jira.codehaus.org/browse/WAGON-215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed WAGON-215. -- Assignee: Brett Porter Resolution: Fixed Fix Version/s: (was: 1.0) 1.0-beta-3 > sftp is much slower than scp for equivalent requests > > > Key: WAGON-215 > URL: http://jira.codehaus.org/browse/WAGON-215 > Project: Maven Wagon > Issue Type: Bug > Components: wagon-ssh >Affects Versions: 1.0-beta-2 >Reporter: Brett Porter >Assignee: Brett Porter > Fix For: 1.0-beta-3 > > > even though it doesn't fork any processes, sftp is much slower than scp for > equivalent requests in my environment (45 seconds vs 2 mins 15 seconds for a > snapshot upload). > Consider profiling the process to see what consumes the time. -- 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
[jira] Updated: (MPLUGIN-120) Update to Doxia 1.0-beta-1
[ http://jira.codehaus.org/browse/MPLUGIN-120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl updated MPLUGIN-120: -- Fix Version/s: 2.5 > Update to Doxia 1.0-beta-1 > -- > > Key: MPLUGIN-120 > URL: http://jira.codehaus.org/browse/MPLUGIN-120 > Project: Maven 2.x Plugin Tools > Issue Type: Task > Components: Plugin Plugin >Reporter: Lukas Theussl > Fix For: 2.5 > > -- 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
[jira] Commented: (DOXIASITETOOLS-10) Adds test for docbook module
[ http://jira.codehaus.org/browse/DOXIASITETOOLS-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=137024#action_137024 ] Max Berger commented on DOXIASITETOOLS-10: -- Lukas, yes, exactly the same setup except for OS. All machines run maven 2.0.9, all machines use the same project, the invocation is "mvn site". http://jeuclid.svn.sourceforge.net/svnroot/jeuclid/trunk/ (now with the explicit fix) I tried with Sun JDK 1.6 under Linux, and the docbook pages are rendered just fine. I tried with Apple JDK 1.5 (32bit. 64 bit), and Apple JDK 1.6 (64 bit) on two different machines, docbook pages are silently ignored. Unfortunately I was not able to replicate the behavior with the doxia beta standalone, so I assumed it is fixed and did not file a bug for this. However, if you are interested I can try to investigate this further. Max > Adds test for docbook module > > > Key: DOXIASITETOOLS-10 > URL: http://jira.codehaus.org/browse/DOXIASITETOOLS-10 > Project: Maven Doxia Sitetools > Issue Type: Test > Components: Site renderer >Reporter: Max Berger >Assignee: Lukas Theussl > Fix For: 1.0-beta-1 > > Attachments: docbookTest.patch > > > This patch adds an assertion to check if a docbook page could be rendered. > Background: Maven 2.0.9 fails to render docbook pages on OS X, and I tried > reproducing this with this testcase. Unfortunately I was unable to reprocude > the error: doxia-site-tools always generates the page as it should -> Looks > like I'll have to wait for maven to use the newer doxia version. -- 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
[jira] Created: (MANTTASKS-111) Support for SNAPSHOT deployment
Support for SNAPSHOT deployment --- Key: MANTTASKS-111 URL: http://jira.codehaus.org/browse/MANTTASKS-111 Project: Maven 2.x Ant Tasks Issue Type: Bug Components: deploy task Affects Versions: 2.0.9 Reporter: Dave Syer Maybe there is some support for SNAPSHOT deployment in the ant tasks, but the documentation (just one page?) doesn't show any features or examples. Please provide the ability to upload snapshots to a remote Maven repository (like mvn deploy). -- 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
[jira] Commented: (DOXIASITETOOLS-10) Adds test for docbook module
[ http://jira.codehaus.org/browse/DOXIASITETOOLS-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=137026#action_137026 ] Lukas Theussl commented on DOXIASITETOOLS-10: - Since it works now there is no need for further investigation.. ;) The setup above is how it should work anyway, it has been added to the docs of the site plugin [1] which will be published with the next release. [1] https://svn.apache.org/viewvc?view=rev&revision=616325 > Adds test for docbook module > > > Key: DOXIASITETOOLS-10 > URL: http://jira.codehaus.org/browse/DOXIASITETOOLS-10 > Project: Maven Doxia Sitetools > Issue Type: Test > Components: Site renderer >Reporter: Max Berger >Assignee: Lukas Theussl > Fix For: 1.0-beta-1 > > Attachments: docbookTest.patch > > > This patch adds an assertion to check if a docbook page could be rendered. > Background: Maven 2.0.9 fails to render docbook pages on OS X, and I tried > reproducing this with this testcase. Unfortunately I was unable to reprocude > the error: doxia-site-tools always generates the page as it should -> Looks > like I'll have to wait for maven to use the newer doxia version. -- 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
[jira] Commented: (DOXIASITETOOLS-10) Adds test for docbook module
[ http://jira.codehaus.org/browse/DOXIASITETOOLS-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=137020#action_137020 ] Lukas Theussl commented on DOXIASITETOOLS-10: - Are you sure you have exactly the same setup on both machines? Maybe the docbook module gets loaded by some other (transitive) dependency, which makes the component lookup work (try -X to see if and where it gets loaded). > Adds test for docbook module > > > Key: DOXIASITETOOLS-10 > URL: http://jira.codehaus.org/browse/DOXIASITETOOLS-10 > Project: Maven Doxia Sitetools > Issue Type: Test > Components: Site renderer >Reporter: Max Berger >Assignee: Lukas Theussl > Fix For: 1.0-beta-1 > > Attachments: docbookTest.patch > > > This patch adds an assertion to check if a docbook page could be rendered. > Background: Maven 2.0.9 fails to render docbook pages on OS X, and I tried > reproducing this with this testcase. Unfortunately I was unable to reprocude > the error: doxia-site-tools always generates the page as it should -> Looks > like I'll have to wait for maven to use the newer doxia version. -- 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
[jira] Created: (MPLUGIN-120) Update to Doxia 1.0-beta-1
Update to Doxia 1.0-beta-1 -- Key: MPLUGIN-120 URL: http://jira.codehaus.org/browse/MPLUGIN-120 Project: Maven 2.x Plugin Tools Issue Type: Task Components: Plugin Plugin Reporter: Lukas Theussl Fix For: 2.5 -- 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
[jira] Created: (SCM-381) Extend API to support remote commands like rlist, rlog
Extend API to support remote commands like rlist, rlog
--
Key: SCM-381
URL: http://jira.codehaus.org/browse/SCM-381
Project: Maven SCM
Issue Type: New Feature
Components: maven-scm-api
Affects Versions: 1.x
Reporter: Sergey Zakusov
We propose to extend the existing API to support some remote commands - it's a
really required feature to allow work with SCMs without Working Copies.
For a start there should be done the following commands:
# *rlist* - to list remotely repository entries;
# *rinfo* - to get information about repository entries;
# *rlog* - to get change log of repository entries;
# *rcat* - to get file contents remotely.
It can be specified as a new interface extended from ScmManager:
{code:title=ScmRemoteManager.java|bolderStyle=solid}
public interface ScmRemoteManager extends ScmManager {
/**
* Lists remotely each element specified by i_fileSet in the
repository.
*
* @param i_repository the source control system to use
* @param i_fileSet the entries (files and/or directories) to list
* @param i_recursive descend recursively
* @param i_version use the version defined by the branch/tag/revision
* @return The list of entries in the repository
* @throws ScmException if the command cannot be performed
* @see ScmManager#list(ScmRepository, ScmFileSet, boolean, ScmVersion) to
work with Working Copy
*/
ListScmResult rlist(ScmRepository i_repository, ScmFileSet i_fileSet,
boolean i_recursive, ScmVersion i_version)
throws ScmException;
/**
* Retrieves information about each remote element specified by
i_fileSet.
*
* @param i_repository the source control system to use
* @param i_fileSet the entries (files and/or directories) to get
information
* @param i_version the branch/tag/revision to use
* @return Information about each requested entry from the repository
* @throws ScmException if the command cannot be performed
*/
InfoScmResult rinfo(ScmRepository i_repository, ScmFileSet i_fileSet,
ScmVersion i_version) throws ScmException;
/**
* Retrieves log information about each remote element specified by
i_fileSet.
*
* @param i_repository the source control system to use
* @param i_fileSet the entries (files and/or directories) to get
information
* @param i_startVersion the start branch/tag/revision
* @param i_endVersion the end branch/tag/revision
* @return Log information about each requested entry from the repository
* @throws ScmException if the command cannot be performed
* @see ScmManager#changeLog(ScmRepository, ScmFileSet, ScmVersion,
ScmVersion) to work with Working Copy
*/
ChangeLogScmResult rlog(ScmRepository i_repository, ScmFileSet i_fileSet,
ScmVersion i_startVersion,
ScmVersion i_endVersion) throws ScmException;
/**
* Fetches the contents and/or properties of each remote element specified
by i_fileSet.
*
* @param i_repository the source control system to use
* @param i_fileSet the files to get content
* @param i_version the branch/tag/revision to use
* @return Contents and/or properties of each requested file from the
repository
* @throws ScmException if the command cannot be performed
*/
CatScmResult rcat(ScmRepository i_repository, ScmFileSet i_fileSet,
ScmVersion i_version) throws ScmException;
}
{code}
--
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
[jira] Updated: (MSITE-257) Double quote character rendered as entity, which breaks JavaScript
[
http://jira.codehaus.org/browse/MSITE-257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lukas Theussl updated MSITE-257:
Fix Version/s: 2.0-beta-8
> Double quote character rendered as entity, which breaks JavaScript
> --
>
> Key: MSITE-257
> URL: http://jira.codehaus.org/browse/MSITE-257
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
>Affects Versions: 2.0-beta-5
> Environment: Maven 2.0.7, Maven Site Plugin 2.0-beta-5
>Reporter: Wendy Smoak
>Priority: Trivial
> Fix For: 2.0-beta-8
>
> Attachments: mysite.zip
>
>
> When a simple script is included in xdoc source, the double characters get
> rendered as the html entity " and the script does not execute.
> For example, this in xdoc
>alert("Hello!");
> produces this in the rendered html:
>alert("Hello!");
> Sample project attached. Execute 'mvn site:run', visit
> http://localhost:8080/index.html, and view the source of the page.
> (Brian Fox discovered this while adding the Google search box to the Maven
> site.)
--
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
[jira] Commented: (MSITE-307) Site generation broken with multi-module property inheritence
[
http://jira.codehaus.org/browse/MSITE-307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=137037#action_137037
]
Thomas Schmidt commented on MSITE-307:
--
I have the exact same Problem.
I think it is even worse. I get a BUILD ERROR when running the site phase.
Excerpt from my Maven run - executed from the main directory of my multimodule
project:
==
[INFO] [site:site]
[INFO] Not executing cobertura:report as the cobertura data file
(D:\schmidt\eclipse\mdb\build-tools\target\cobertura\cobertura.ser) could not
be found
Downloading:
http://myserver/repos/com/my-app/mdb/mdb/${com.my-app.mdb.version}/mdb-${com.my-app.mdb.version}.pom
Downloading:
http://people.apache.org/repo/m2-snapshot-repository/com/my-app/mdb/mdb/${com.my-app.mdb.version}/mdb-${com.my-app.mdb.version}.pom
Downloading:
http://people.apache.org/repo/m2-incubating-repository/com/my-app/mdb/mdb/${com.my-app.mdb.version}/mdb-${com.my-app.mdb.version}.pom
Downloading:
http://download.java.net/maven/1/com.my-app.mdb/poms/mdb-${com.my-app.mdb.version}.pom
Downloading:
http://repo1.maven.org/maven2/com/my-app/mdb/mdb/${com.my-app.mdb.version}/mdb-${com.my-app.mdb.version}.pom
[INFO] Parent project loaded from repository.
Downloading:
http://myserver/repos/com/my-app/mdb/mdb/${com.my-app.mdb.version}/mdb-${com.my-app.mdb.version}-site_en.xml
Downloading:
http://people.apache.org/repo/m2-snapshot-repository/com/my-app/mdb/mdb/${com.my-app.mdb.version}/mdb-${com.my-app.mdb.version}-site_en.xml
Downloading:
http://people.apache.org/repo/m2-incubating-repository/com/my-app/mdb/mdb/${com.my-app.mdb.version}/mdb-${com.my-app.mdb.version}-site_en.xml
Downloading:
http://download.java.net/maven/1/com.my-app.mdb/xmls/mdb-${com.my-app.mdb.version}-site_en.xml
Downloading:
http://repo1.maven.org/maven2/com/my-app/mdb/mdb/${com.my-app.mdb.version}/mdb-${com.my-app.mdb.version}-site_en.xml
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] The site descriptor cannot be resolved from the repository: The system
can not find the specified path
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 12 seconds
[INFO] Finished at: Mon Jun 02 14:06:53 CEST 2008
[INFO] Final Memory: 36M/254M
[INFO]
==
The Properties like ${com.my-app.mdb.version} are specified in my root POM and
only used there and in the POMs of the modules. In all other phases and goals
they can be resolved from anywhere in the project.
It seems that the site plugin does not resolve those properties at all.
This is really urgent to me as I can not build any reports without hard coding
the version numbers in my various modules!
If there is anything I can do to help, please tell me!
Thx!
> Site generation broken with multi-module property inheritence
> -
>
> Key: MSITE-307
> URL: http://jira.codehaus.org/browse/MSITE-307
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
> Components: inheritance
>Affects Versions: 2.0-beta-6
> Environment: Ubuntu 7.10, Maven 2.0.8
>Reporter: Eric Ryan
>
> Maven2 site plugin inheritence
> I have a multi-module project with the following directory structure:
> my-app
> |
> |---my-client-ui
> | |
> | |---pom.xml
> |
> |---my-core
> | |
> | |---pom.xml
> |
> |---my-common
> | |
> | |---pom.xml
> |
> |---pom.xml
> I define properties such as ${myVersion}, ${myArtifactId}, ${myGroupId} in
> the parent pom. These properties are used by the child poms to resolve the
> parent pom (they are used in the tags). These properties are
> inherited by the children (as expected) when running goals such as clean,
> package, or install.
> I start to see problems when I try to use the site plugin. I first run the
> install goal to install my project's jars and poms into my local
> repo(~/.m2/repository/). I then verify that the jars and poms are in my
> local repo. When I try to run the site plugin it seems as though maven is
> unable to interpret the properties defined in the parent pom. I receive the
> following output for each module:
> [INFO]
>
> [INFO] Building my-client-ui
> [INFO]task-segment: [site]
> [INFO]
>
> [INFO] [site:site]
>
[jira] Issue Comment Edited: (MSITE-307) Site generation broken with multi-module property inheritence
[
http://jira.codehaus.org/browse/MSITE-307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=137037#action_137037
]
mithrandir edited comment on MSITE-307 at 6/2/08 7:19 AM:
--
I have the exact same problem.
I think it is even worse. I get a BUILD ERROR when running the site phase.
Excerpt from my Maven run - executed from the main directory of my multimodule
project:
==
[INFO] [site:site]
[INFO] Not executing cobertura:report as the cobertura data file
(D:\schmidt\eclipse\mdb\build-tools\target\cobertura\cobertura.ser) could not
be found
Downloading:
http://myserver/repos/com/my-app/mdb/mdb/${com.my-app.mdb.version}/mdb-${com.my-app.mdb.version}.pom
Downloading:
http://people.apache.org/repo/m2-snapshot-repository/com/my-app/mdb/mdb/${com.my-app.mdb.version}/mdb-${com.my-app.mdb.version}.pom
Downloading:
http://people.apache.org/repo/m2-incubating-repository/com/my-app/mdb/mdb/${com.my-app.mdb.version}/mdb-${com.my-app.mdb.version}.pom
Downloading:
http://download.java.net/maven/1/com.my-app.mdb/poms/mdb-${com.my-app.mdb.version}.pom
Downloading:
http://repo1.maven.org/maven2/com/my-app/mdb/mdb/${com.my-app.mdb.version}/mdb-${com.my-app.mdb.version}.pom
[INFO] Parent project loaded from repository.
Downloading:
http://myserver/repos/com/my-app/mdb/mdb/${com.my-app.mdb.version}/mdb-${com.my-app.mdb.version}-site_en.xml
Downloading:
http://people.apache.org/repo/m2-snapshot-repository/com/my-app/mdb/mdb/${com.my-app.mdb.version}/mdb-${com.my-app.mdb.version}-site_en.xml
Downloading:
http://people.apache.org/repo/m2-incubating-repository/com/my-app/mdb/mdb/${com.my-app.mdb.version}/mdb-${com.my-app.mdb.version}-site_en.xml
Downloading:
http://download.java.net/maven/1/com.my-app.mdb/xmls/mdb-${com.my-app.mdb.version}-site_en.xml
Downloading:
http://repo1.maven.org/maven2/com/my-app/mdb/mdb/${com.my-app.mdb.version}/mdb-${com.my-app.mdb.version}-site_en.xml
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] The site descriptor cannot be resolved from the repository: The system
can not find the specified path
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 12 seconds
[INFO] Finished at: Mon Jun 02 14:06:53 CEST 2008
[INFO] Final Memory: 36M/254M
[INFO]
==
The Properties like ${com.my-app.mdb.version} are specified in my root POM and
only used there and in the POMs of the modules. In all other phases and goals
they can be resolved from anywhere in the project.
It seems that the site plugin does not resolve those properties at all.
This is really urgent to me as I can not build any reports without hard coding
the version numbers in my various modules!
If there is anything I can do to help, please tell me!
Thx!
was (Author: mithrandir):
I have the exact same Problem.
I think it is even worse. I get a BUILD ERROR when running the site phase.
Excerpt from my Maven run - executed from the main directory of my multimodule
project:
==
[INFO] [site:site]
[INFO] Not executing cobertura:report as the cobertura data file
(D:\schmidt\eclipse\mdb\build-tools\target\cobertura\cobertura.ser) could not
be found
Downloading:
http://myserver/repos/com/my-app/mdb/mdb/${com.my-app.mdb.version}/mdb-${com.my-app.mdb.version}.pom
Downloading:
http://people.apache.org/repo/m2-snapshot-repository/com/my-app/mdb/mdb/${com.my-app.mdb.version}/mdb-${com.my-app.mdb.version}.pom
Downloading:
http://people.apache.org/repo/m2-incubating-repository/com/my-app/mdb/mdb/${com.my-app.mdb.version}/mdb-${com.my-app.mdb.version}.pom
Downloading:
http://download.java.net/maven/1/com.my-app.mdb/poms/mdb-${com.my-app.mdb.version}.pom
Downloading:
http://repo1.maven.org/maven2/com/my-app/mdb/mdb/${com.my-app.mdb.version}/mdb-${com.my-app.mdb.version}.pom
[INFO] Parent project loaded from repository.
Downloading:
http://myserver/repos/com/my-app/mdb/mdb/${com.my-app.mdb.version}/mdb-${com.my-app.mdb.version}-site_en.xml
Downloading:
http://people.apache.org/repo/m2-snapshot-repository/com/my-app/mdb/mdb/${com.my-app.mdb.version}/mdb-${com.my-app.mdb.version}-site_en.xml
Downloading:
http://people.apache.org/repo/m2-incubating-repository/com/my-app/mdb/mdb/${com.my-app.mdb.version}/mdb-${com.my-app.mdb.version}-site_en.xml
Downloading:
http://download.java.net/maven/1/com.my-app.mdb/xmls/mdb-${com.my-app.mdb.versi
[jira] Issue Comment Edited: (MSITE-307) Site generation broken with multi-module property inheritence
[
http://jira.codehaus.org/browse/MSITE-307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=137037#action_137037
]
mithrandir edited comment on MSITE-307 at 6/2/08 7:29 AM:
--
I have the exact same problem.
I think it is even worse. I get a BUILD ERROR when running the site phase.
Excerpt from my Maven run - executed from the main directory of my multimodule
project:
==
[INFO] [site:site]
[INFO] Not executing cobertura:report as the cobertura data file
(D:\schmidt\eclipse\mdb\build-tools\target\cobertura\cobertura.ser) could not
be found
Downloading:
http://myserver/repos/com/my-app/mdb/mdb/${com.my-app.mdb.version}/mdb-${com.my-app.mdb.version}.pom
Downloading:
http://people.apache.org/repo/m2-snapshot-repository/com/my-app/mdb/mdb/${com.my-app.mdb.version}/mdb-${com.my-app.mdb.version}.pom
Downloading:
http://people.apache.org/repo/m2-incubating-repository/com/my-app/mdb/mdb/${com.my-app.mdb.version}/mdb-${com.my-app.mdb.version}.pom
Downloading:
http://download.java.net/maven/1/com.my-app.mdb/poms/mdb-${com.my-app.mdb.version}.pom
Downloading:
http://repo1.maven.org/maven2/com/my-app/mdb/mdb/${com.my-app.mdb.version}/mdb-${com.my-app.mdb.version}.pom
[INFO] Parent project loaded from repository.
Downloading:
http://myserver/repos/com/my-app/mdb/mdb/${com.my-app.mdb.version}/mdb-${com.my-app.mdb.version}-site_en.xml
Downloading:
http://people.apache.org/repo/m2-snapshot-repository/com/my-app/mdb/mdb/${com.my-app.mdb.version}/mdb-${com.my-app.mdb.version}-site_en.xml
Downloading:
http://people.apache.org/repo/m2-incubating-repository/com/my-app/mdb/mdb/${com.my-app.mdb.version}/mdb-${com.my-app.mdb.version}-site_en.xml
Downloading:
http://download.java.net/maven/1/com.my-app.mdb/xmls/mdb-${com.my-app.mdb.version}-site_en.xml
Downloading:
http://repo1.maven.org/maven2/com/my-app/mdb/mdb/${com.my-app.mdb.version}/mdb-${com.my-app.mdb.version}-site_en.xml
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] The site descriptor cannot be resolved from the repository: The system
can not find the specified path
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 12 seconds
[INFO] Finished at: Mon Jun 02 14:06:53 CEST 2008
[INFO] Final Memory: 36M/254M
[INFO]
==
The Properties like ${com.my-app.mdb.version} are specified in my root POM and
only used there and in the POMs of the modules. In all other phases and goals
they can be resolved from anywhere in the project.
I already tread replacing the periods with underscores, too. That didn't help
either!
It seems that the site plugin does not resolve those properties at all.
This is really urgent to me as I can not build any reports without hard coding
the version numbers in my various modules!
If there is anything I can do to help, please tell me!
Thx!
was (Author: mithrandir):
I have the exact same problem.
I think it is even worse. I get a BUILD ERROR when running the site phase.
Excerpt from my Maven run - executed from the main directory of my multimodule
project:
==
[INFO] [site:site]
[INFO] Not executing cobertura:report as the cobertura data file
(D:\schmidt\eclipse\mdb\build-tools\target\cobertura\cobertura.ser) could not
be found
Downloading:
http://myserver/repos/com/my-app/mdb/mdb/${com.my-app.mdb.version}/mdb-${com.my-app.mdb.version}.pom
Downloading:
http://people.apache.org/repo/m2-snapshot-repository/com/my-app/mdb/mdb/${com.my-app.mdb.version}/mdb-${com.my-app.mdb.version}.pom
Downloading:
http://people.apache.org/repo/m2-incubating-repository/com/my-app/mdb/mdb/${com.my-app.mdb.version}/mdb-${com.my-app.mdb.version}.pom
Downloading:
http://download.java.net/maven/1/com.my-app.mdb/poms/mdb-${com.my-app.mdb.version}.pom
Downloading:
http://repo1.maven.org/maven2/com/my-app/mdb/mdb/${com.my-app.mdb.version}/mdb-${com.my-app.mdb.version}.pom
[INFO] Parent project loaded from repository.
Downloading:
http://myserver/repos/com/my-app/mdb/mdb/${com.my-app.mdb.version}/mdb-${com.my-app.mdb.version}-site_en.xml
Downloading:
http://people.apache.org/repo/m2-snapshot-repository/com/my-app/mdb/mdb/${com.my-app.mdb.version}/mdb-${com.my-app.mdb.version}-site_en.xml
Downloading:
http://people.apache.org/repo/m2-incubating-repository/com/my-app/mdb/mdb/${com.my-app.mdb.version}/mdb-${com.my-app.mdb.version}-site_en.xml
Downlo
[jira] Commented: (MPIR-101) Update to Doxia 1.0-beta-1
[ http://jira.codehaus.org/browse/MPIR-101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=137040#action_137040 ] Lukas Theussl commented on MPIR-101: Branch to test: https://svn.apache.org/repos/asf/maven/plugins/branches/maven-project-info-reports-plugin-doxia-beta-1/ I also deployed a snapshot (2.2-SNAPSHOT, use with maven-2.0.10-SNAPSHOT!) > Update to Doxia 1.0-beta-1 > -- > > Key: MPIR-101 > URL: http://jira.codehaus.org/browse/MPIR-101 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Task >Affects Versions: 2.1 >Reporter: Dennis Lundberg > Fix For: 2.2 > > -- 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
[jira] Commented: (MSITE-298) Update to Doxia 1.0-beta-1
[ http://jira.codehaus.org/browse/MSITE-298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=137039#action_137039 ] Lukas Theussl commented on MSITE-298: - Branch to test: https://svn.apache.org/repos/asf/maven/plugins/branches/maven-site-plugin-doxia-beta-1/ I also deployed a snapshot (2.0-beta-8-SNAPSHOT, use with maven-2.0.10-SNAPSHOT!) > Update to Doxia 1.0-beta-1 > -- > > Key: MSITE-298 > URL: http://jira.codehaus.org/browse/MSITE-298 > Project: Maven 2.x Site Plugin > Issue Type: Task >Affects Versions: 2.0-beta-6 >Reporter: Vincent Siveton > Fix For: 2.0-beta-8 > > -- 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
[jira] Issue Comment Edited: (MSITE-307) Site generation broken with multi-module property inheritence
[
http://jira.codehaus.org/browse/MSITE-307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=137037#action_137037
]
mithrandir edited comment on MSITE-307 at 6/2/08 7:33 AM:
--
I have exactly the same problem.
I think it is even worse. I get a BUILD ERROR when running the site phase.
Excerpt from my Maven run - executed from the main directory of my multimodule
project:
==
[INFO] [site:site]
[INFO] Not executing cobertura:report as the cobertura data file
(D:\schmidt\eclipse\mdb\build-tools\target\cobertura\cobertura.ser) could not
be found
Downloading:
http://myserver/repos/com/my-app/mdb/mdb/${com.my-app.mdb.version}/mdb-${com.my-app.mdb.version}.pom
Downloading:
http://people.apache.org/repo/m2-snapshot-repository/com/my-app/mdb/mdb/${com.my-app.mdb.version}/mdb-${com.my-app.mdb.version}.pom
Downloading:
http://people.apache.org/repo/m2-incubating-repository/com/my-app/mdb/mdb/${com.my-app.mdb.version}/mdb-${com.my-app.mdb.version}.pom
Downloading:
http://download.java.net/maven/1/com.my-app.mdb/poms/mdb-${com.my-app.mdb.version}.pom
Downloading:
http://repo1.maven.org/maven2/com/my-app/mdb/mdb/${com.my-app.mdb.version}/mdb-${com.my-app.mdb.version}.pom
[INFO] Parent project loaded from repository.
Downloading:
http://myserver/repos/com/my-app/mdb/mdb/${com.my-app.mdb.version}/mdb-${com.my-app.mdb.version}-site_en.xml
Downloading:
http://people.apache.org/repo/m2-snapshot-repository/com/my-app/mdb/mdb/${com.my-app.mdb.version}/mdb-${com.my-app.mdb.version}-site_en.xml
Downloading:
http://people.apache.org/repo/m2-incubating-repository/com/my-app/mdb/mdb/${com.my-app.mdb.version}/mdb-${com.my-app.mdb.version}-site_en.xml
Downloading:
http://download.java.net/maven/1/com.my-app.mdb/xmls/mdb-${com.my-app.mdb.version}-site_en.xml
Downloading:
http://repo1.maven.org/maven2/com/my-app/mdb/mdb/${com.my-app.mdb.version}/mdb-${com.my-app.mdb.version}-site_en.xml
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] The site descriptor cannot be resolved from the repository: The system
can not find the specified path
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 12 seconds
[INFO] Finished at: Mon Jun 02 14:06:53 CEST 2008
[INFO] Final Memory: 36M/254M
[INFO]
==
The Properties like ${com.my-app.mdb.version} are specified in my root POM and
only used there and in the POMs of the modules. In all other phases and goals
they can be resolved from anywhere in the project.
I already tread replacing the periods with underscores, too. That didn't help
either!
It seems that the site plugin does not resolve those properties at all.
This is really urgent to me as I can not build any reports without hard coding
the version numbers in my various modules!
If there is anything I can do to help, please tell me!
Thx!
was (Author: mithrandir):
I have the exact same problem.
I think it is even worse. I get a BUILD ERROR when running the site phase.
Excerpt from my Maven run - executed from the main directory of my multimodule
project:
==
[INFO] [site:site]
[INFO] Not executing cobertura:report as the cobertura data file
(D:\schmidt\eclipse\mdb\build-tools\target\cobertura\cobertura.ser) could not
be found
Downloading:
http://myserver/repos/com/my-app/mdb/mdb/${com.my-app.mdb.version}/mdb-${com.my-app.mdb.version}.pom
Downloading:
http://people.apache.org/repo/m2-snapshot-repository/com/my-app/mdb/mdb/${com.my-app.mdb.version}/mdb-${com.my-app.mdb.version}.pom
Downloading:
http://people.apache.org/repo/m2-incubating-repository/com/my-app/mdb/mdb/${com.my-app.mdb.version}/mdb-${com.my-app.mdb.version}.pom
Downloading:
http://download.java.net/maven/1/com.my-app.mdb/poms/mdb-${com.my-app.mdb.version}.pom
Downloading:
http://repo1.maven.org/maven2/com/my-app/mdb/mdb/${com.my-app.mdb.version}/mdb-${com.my-app.mdb.version}.pom
[INFO] Parent project loaded from repository.
Downloading:
http://myserver/repos/com/my-app/mdb/mdb/${com.my-app.mdb.version}/mdb-${com.my-app.mdb.version}-site_en.xml
Downloading:
http://people.apache.org/repo/m2-snapshot-repository/com/my-app/mdb/mdb/${com.my-app.mdb.version}/mdb-${com.my-app.mdb.version}-site_en.xml
Downloading:
http://people.apache.org/repo/m2-incubating-repository/com/my-app/mdb/mdb/${com.my-app.mdb.version}/mdb-${com.my-app.mdb.version}-site_en.xml
Down
[jira] Created: (MASSEMBLY-328) When assembly is attached to pom with appendAssemblyId disabled, it won't be installed or deployed
When assembly is attached to pom with appendAssemblyId disabled, it won't be installed or deployed -- Key: MASSEMBLY-328 URL: http://jira.codehaus.org/browse/MASSEMBLY-328 Project: Maven 2.x Assembly Plugin Issue Type: Bug Affects Versions: 2.2-beta-2 Environment: Windows XP SP3 with cygwin Reporter: Bugittaa Pahasti Attachments: assembly-id-test.zip The use case applies to multi module build, but because it also occurs in a case of single pom, I'll use that as a example. The zip generated in the attached example is installed nicely when appendAssemblyId is true. When it is false, the following is logged: "[WARNING] Configuration options: 'appendAssemblyId' is set to false, and 'classifier' is missing. Instead of attaching the assembly file: c:\code\test\test3\target\assembly-test-1.0-SNAPSHOT.zip, it will become the file for main project artifact. NOTE: If multiple descriptors or descriptor-formats are provided for this project, the value of this file will be non-deterministic!" However, only pom.xml is installed/deployed. -- 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
[jira] Created: (MDEP-170) Endless loop with relocation jtds:jtds
Endless loop with relocation jtds:jtds -- Key: MDEP-170 URL: http://jira.codehaus.org/browse/MDEP-170 Project: Maven 2.x Dependency Plugin Issue Type: Bug Environment: WinXP maven 2.0.9 Reporter: bartvdc Assignee: Brian Fox Priority: Minor Attachments: dependencybug.zip I'm getting an endless loop when installing a project using jtds:jtds. I can see in the pom that it's relocated to net.sourceforge.jtds. Output says : [WARNING] While downloading net.sourceforge.jtds:jtds:1.2 This artifact has been relocated to net.sourceforge.jtds:jtds:1.2. -- 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
[jira] Updated: (MDEP-170) Endless loop with relocation jtds:jtds
[ http://jira.codehaus.org/browse/MDEP-170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox updated MDEP-170: --- I've seen this before in the 2.0.7 timeframe but could never reproduce it. > Endless loop with relocation jtds:jtds > -- > > Key: MDEP-170 > URL: http://jira.codehaus.org/browse/MDEP-170 > Project: Maven 2.x Dependency Plugin > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 2.0.7, 2.0.8, 2.0.9 > Environment: WinXP maven 2.0.9 >Reporter: bartvdc >Assignee: Brian Fox >Priority: Minor > Fix For: 2.0.10 > > Attachments: dependencybug.zip > > > I'm getting an endless loop when installing a project using jtds:jtds. > I can see in the pom that it's relocated to net.sourceforge.jtds. > Output says : > [WARNING] While downloading net.sourceforge.jtds:jtds:1.2 > This artifact has been relocated to net.sourceforge.jtds:jtds:1.2. -- 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
[jira] Moved: (MNG-3610) Endless loop with relocation jtds:jtds
[ http://jira.codehaus.org/browse/MNG-3610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox moved MDEP-170 to MNG-3610: - Complexity: Intermediate Key: MNG-3610 (was: MDEP-170) Project: Maven 2 (was: Maven 2.x Dependency Plugin) > Endless loop with relocation jtds:jtds > -- > > Key: MNG-3610 > URL: http://jira.codehaus.org/browse/MNG-3610 > Project: Maven 2 > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 2.0.7, 2.0.8, 2.0.9 > Environment: WinXP maven 2.0.9 >Reporter: bartvdc >Assignee: Brian Fox >Priority: Minor > Fix For: 2.0.10 > > Attachments: dependencybug.zip > > > I'm getting an endless loop when installing a project using jtds:jtds. > I can see in the pom that it's relocated to net.sourceforge.jtds. > Output says : > [WARNING] While downloading net.sourceforge.jtds:jtds:1.2 > This artifact has been relocated to net.sourceforge.jtds:jtds:1.2. -- 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
[jira] Updated: (MNG-3610) Endless loop with relocation jtds:jtds
[ http://jira.codehaus.org/browse/MNG-3610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox updated MNG-3610: --- Affects Version/s: 2.0.7 2.0.8 2.0.9 Fix Version/s: 2.0.10 Component/s: Artifacts and Repositories > Endless loop with relocation jtds:jtds > -- > > Key: MNG-3610 > URL: http://jira.codehaus.org/browse/MNG-3610 > Project: Maven 2 > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 2.0.7, 2.0.8, 2.0.9 > Environment: WinXP maven 2.0.9 >Reporter: bartvdc >Assignee: Brian Fox >Priority: Minor > Fix For: 2.0.10 > > Attachments: dependencybug.zip > > > I'm getting an endless loop when installing a project using jtds:jtds. > I can see in the pom that it's relocated to net.sourceforge.jtds. > Output says : > [WARNING] While downloading net.sourceforge.jtds:jtds:1.2 > This artifact has been relocated to net.sourceforge.jtds:jtds:1.2. -- 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
[jira] Commented: (MAVENUPLOAD-2082) SubEtha SMTP 2.0.1
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=137071#action_137071 ] Geoffrey Wiseman commented on MAVENUPLOAD-2082: --- Ugh. Sorry, PEBKAC on that one. Internal server name, didn't translate it: http://64.34.27.174/artifactory/repo/org/subethamail/subethasmtp/2.0.1/subethasmtp-2.0.1-bundle.jar > SubEtha SMTP 2.0.1 > -- > > Key: MAVENUPLOAD-2082 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2082 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Geoffrey Wiseman > > http://spatium/artifactory/repo/org/subethamail/subethasmtp/2.0.1/subethasmtp-2.0.1-bundle.jar > http://subethasmtp.tigris.org/ > I'm not a member of the subetha team, although I do have their blessing to > send this up (http://subethasmtp.tigris.org/issues/show_bug.cgi?id=11). -- 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
[jira] Closed: (WAGON-219) support getIfNewer in scp wagon
[ http://jira.codehaus.org/browse/WAGON-219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed WAGON-219. -- Assignee: Brett Porter Resolution: Fixed Fix Version/s: 1.0-beta-3 > support getIfNewer in scp wagon > --- > > Key: WAGON-219 > URL: http://jira.codehaus.org/browse/WAGON-219 > Project: Maven Wagon > Issue Type: New Feature > Components: wagon-ssh >Reporter: Brett Porter >Assignee: Brett Porter > Fix For: 1.0-beta-3 > > -- 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
[jira] Created: (WAGON-219) support getIfNewer in scp wagon
support getIfNewer in scp wagon --- Key: WAGON-219 URL: http://jira.codehaus.org/browse/WAGON-219 Project: Maven Wagon Issue Type: New Feature Components: wagon-ssh Reporter: Brett Porter Fix For: 1.0-beta-3 -- 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
[jira] Created: (DOXIA-245) Xdoc parser should generate anchors for id attributes of section or subsection
Xdoc parser should generate anchors for id attributes of section or subsection -- Key: DOXIA-245 URL: http://jira.codehaus.org/browse/DOXIA-245 Project: Maven Doxia Issue Type: New Feature Components: Module - Xdoc Affects Versions: 1.0-alpha-11 Reporter: Lukas Theussl Fix For: 1.0-beta-1 A la m1: http://maven.apache.org/maven-1.x/plugins/xdoc/reference/xdocs.html#Referencing_sections_and_subsections -- 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
[jira] Updated: (DOXIA-245) Xdoc parser should generate anchors for id attributes of section or subsection
[ http://jira.codehaus.org/browse/DOXIA-245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl updated DOXIA-245: Assignee: Lukas Theussl Fix Version/s: 1.0-beta-1 > Xdoc parser should generate anchors for id attributes of section or subsection > -- > > Key: DOXIA-245 > URL: http://jira.codehaus.org/browse/DOXIA-245 > Project: Maven Doxia > Issue Type: New Feature > Components: Module - Xdoc >Affects Versions: 1.0-alpha-11 >Reporter: Lukas Theussl >Assignee: Lukas Theussl > Fix For: 1.0-beta-1 > > > A la m1: > http://maven.apache.org/maven-1.x/plugins/xdoc/reference/xdocs.html#Referencing_sections_and_subsections -- 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
[jira] Created: (MSTAGE-6) stage:copy fails with Maven 2.0.9
stage:copy fails with Maven 2.0.9 - Key: MSTAGE-6 URL: http://jira.codehaus.org/browse/MSTAGE-6 Project: Maven 2.x Stage Plugin Issue Type: Bug Affects Versions: 1.0-alpha-1 Environment: Maven 2.0.9, Java 1.5.0_15, Windows XP Reporter: Mark Hobson Attachments: stage.log I get the attached CCE when using stage:copy with Maven 2.0.9. Works fine for 2.0.8. -- 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
[jira] Commented: (MANTTASKS-111) Support for SNAPSHOT deployment
[ http://jira.codehaus.org/browse/MANTTASKS-111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=137090#action_137090 ] Dennis Lundberg commented on MANTTASKS-111: --- The section "Installing and Deploying Your Own Artifacts" talks about deploying to a remote repo. I would imagine that Maven Ant tasks works like Maven in this respect and will deploy to a snapshot repo if the artifact is a SNAPSHOT version. Haven't tried this yet, though. > Support for SNAPSHOT deployment > --- > > Key: MANTTASKS-111 > URL: http://jira.codehaus.org/browse/MANTTASKS-111 > Project: Maven 2.x Ant Tasks > Issue Type: Bug > Components: deploy task >Affects Versions: 2.0.9 >Reporter: Dave Syer > > Maybe there is some support for SNAPSHOT deployment in the ant tasks, but the > documentation (just one page?) doesn't show any features or examples. Please > provide the ability to upload snapshots to a remote Maven repository (like > mvn deploy). -- 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
[jira] Created: (MAVENUPLOAD-2090) rsync-ssh request for yusuke.homeip.net
rsync-ssh request for yusuke.homeip.net --- Key: MAVENUPLOAD-2090 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2090 Project: Maven Upload Requests Issue Type: Task Reporter: Yusuke Yamamoto Hi, I want you guys to add my repository to the automatic setup. "yusuke.homeip.net","[EMAIL PROTECTED]:/Users/mavensync/maven2","rsync_ssh","Yusuke Yamamoto","[EMAIL PROTECTED]",, This domain is hosting the "Twitter4J" project. It's a dyndns domain and no whois info is available. http://yusuke.homeip.net/twitter4j/en/index.html You can verify that I'm the owner of the project by checking the project mailing list. http://yusuke.homeip.net/twitter4j/en/index.html#mailingList http://groups.google.com/group/twitter4j/browse_thread/thread/d742d816e7ecf7a6 Or the license term or the project. http://yusuke.homeip.net/twitter4j/en/index.html#license Thanks, Yusuke -- 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
[jira] Closed: (MCOMPILER-76) jdk 1.4 check doesn't catch Integer.valueOf(int) which is java 5
[
http://jira.codehaus.org/browse/MCOMPILER-76?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MCOMPILER-76.
--
Assignee: Benjamin Bentmann
Resolution: Not A Bug
The {{target}} option merely specifies the class file format used by the byte
code, not the classes/methods invoked by it. What you are looking for is called
cross-compilation. Please see:
- [Compiling Sources Using A Different
JDK|http://maven.apache.org/plugins/maven-compiler-plugin/examples/compile-using-different-jdk.html]
- [javac, Cross-Compilation
Options|http://java.sun.com/j2se/1.5.0/docs/tooldocs/windows/javac.html#crosscomp-options]
> jdk 1.4 check doesn't catch Integer.valueOf(int) which is java 5
> -
>
> Key: MCOMPILER-76
> URL: http://jira.codehaus.org/browse/MCOMPILER-76
> Project: Maven 2.x Compiler Plugin
> Issue Type: Bug
>Affects Versions: 2.0.2
> Environment: windows vista, jdk 1.5.10_12,
>Reporter: russell gordon
>Assignee: Benjamin Bentmann
>Priority: Minor
>
> When building with the following option in the pom :
>
> org.apache.maven.plugins
> maven-compiler-plugin
>
> 1.4
> 1.4
>
>
> Using jdk 1.5.0_12. The check does not catch all java 5 code - specifically
> Integer.valueOf(int).
--
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
[jira] Commented: (MANTTASKS-111) Support for SNAPSHOT deployment
[ http://jira.codehaus.org/browse/MANTTASKS-111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=137093#action_137093 ] Ben Hale commented on MANTTASKS-111: The problem isn't deployment, it's what exactly i required to get it to follow -SNAPSHOT conventions. Because not every build system uses a version number with -SNAPSHOT some sort of munging will need to be done to make that work. But what this munging needs to look like isn't clear. A section in the documentation that describes exactly what will trigger the -SNAPSHOT behavior would be appreciated. > Support for SNAPSHOT deployment > --- > > Key: MANTTASKS-111 > URL: http://jira.codehaus.org/browse/MANTTASKS-111 > Project: Maven 2.x Ant Tasks > Issue Type: Bug > Components: deploy task >Affects Versions: 2.0.9 >Reporter: Dave Syer > > Maybe there is some support for SNAPSHOT deployment in the ant tasks, but the > documentation (just one page?) doesn't show any features or examples. Please > provide the ability to upload snapshots to a remote Maven repository (like > mvn deploy). -- 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
[jira] Closed: (MSTAGE-6) stage:copy fails with Maven 2.0.9
[ http://jira.codehaus.org/browse/MSTAGE-6?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed MSTAGE-6. - Assignee: Brett Porter Resolution: Duplicate > stage:copy fails with Maven 2.0.9 > - > > Key: MSTAGE-6 > URL: http://jira.codehaus.org/browse/MSTAGE-6 > Project: Maven 2.x Stage Plugin > Issue Type: Bug >Affects Versions: 1.0-alpha-1 > Environment: Maven 2.0.9, Java 1.5.0_15, Windows XP >Reporter: Mark Hobson >Assignee: Brett Porter > Attachments: stage.log > > > I get the attached CCE when using stage:copy with Maven 2.0.9. Works fine > for 2.0.8. -- 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
[jira] Created: (MCOMPILER-76) jdk 1.4 check doesn't catch Integer.valueOf(int) which is java 5
jdk 1.4 check doesn't catch Integer.valueOf(int) which is java 5 - Key: MCOMPILER-76 URL: http://jira.codehaus.org/browse/MCOMPILER-76 Project: Maven 2.x Compiler Plugin Issue Type: Bug Affects Versions: 2.0.2 Environment: windows vista, jdk 1.5.10_12, Reporter: russell gordon Priority: Minor When building with the following option in the pom : org.apache.maven.plugins maven-compiler-plugin 1.4 1.4 Using jdk 1.5.0_12. The check does not catch all java 5 code - specifically Integer.valueOf(int). -- 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
[jira] Commented: (MANTTASKS-111) Support for SNAPSHOT deployment
[
http://jira.codehaus.org/browse/MANTTASKS-111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=137105#action_137105
]
Benjamin Bentmann commented on MANTTASKS-111:
-
bq. I doubt that anything else than "-SNAPSHOT" at the end of the version will
work.
Right, compare
[{{DefaultArtifact.isSnapshot()}}|http://svn.apache.org/viewvc/maven/components/branches/maven-2.0.x/maven-artifact/src/main/java/org/apache/maven/artifact/DefaultArtifact.java?view=markup]
> Support for SNAPSHOT deployment
> ---
>
> Key: MANTTASKS-111
> URL: http://jira.codehaus.org/browse/MANTTASKS-111
> Project: Maven 2.x Ant Tasks
> Issue Type: Bug
> Components: deploy task
>Affects Versions: 2.0.9
>Reporter: Dave Syer
>
> Maybe there is some support for SNAPSHOT deployment in the ant tasks, but the
> documentation (just one page?) doesn't show any features or examples. Please
> provide the ability to upload snapshots to a remote Maven repository (like
> mvn deploy).
--
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
[jira] Commented: (MANTTASKS-111) Support for SNAPSHOT deployment
[ http://jira.codehaus.org/browse/MANTTASKS-111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=137103#action_137103 ] Dennis Lundberg commented on MANTTASKS-111: --- I doubt that anything else than "-SNAPSHOT" at the end of the version will work. That is what Maven uses. > Support for SNAPSHOT deployment > --- > > Key: MANTTASKS-111 > URL: http://jira.codehaus.org/browse/MANTTASKS-111 > Project: Maven 2.x Ant Tasks > Issue Type: Bug > Components: deploy task >Affects Versions: 2.0.9 >Reporter: Dave Syer > > Maybe there is some support for SNAPSHOT deployment in the ant tasks, but the > documentation (just one page?) doesn't show any features or examples. Please > provide the ability to upload snapshots to a remote Maven repository (like > mvn deploy). -- 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
[jira] Closed: (WAGON-101) Allow use of streams for get, getIfNewer and put
[ http://jira.codehaus.org/browse/WAGON-101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed WAGON-101. -- Resolution: Fixed > Allow use of streams for get, getIfNewer and put > > > Key: WAGON-101 > URL: http://jira.codehaus.org/browse/WAGON-101 > Project: Maven Wagon > Issue Type: New Feature > Components: wagon-provider-api >Affects Versions: 1.0-beta-3 >Reporter: James William Dumay >Assignee: Brett Porter > Fix For: 1.0-beta-3 > > Attachments: wagon-streaming.patch > > > Allow the use of Streams with get, getIfNewer and put. -- 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
[jira] Updated: (WAGON-68) Separate the interfaces for GET vs PUT
[ http://jira.codehaus.org/browse/WAGON-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated WAGON-68: -- Fix Version/s: (was: 1.0-beta-3) 1.x > Separate the interfaces for GET vs PUT > -- > > Key: WAGON-68 > URL: http://jira.codehaus.org/browse/WAGON-68 > Project: Maven Wagon > Issue Type: New Feature > Components: wagon-provider-api >Affects Versions: 1.0-beta-2 >Reporter: Jason van Zyl > Fix For: 1.x > > > There are cases where I could see simply wanting the GET aspect of a Wagon. > Two cases come to mind: a Grizzly wagon for high-speed GETs from a Jetty > instance running the Grizzly connector; a BT client that would just be doing > GETs. So maybe we could keep the original interfaces and add > WagonRetriever/Getter and WagonPublisher/Putter. -- 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
[jira] Updated: (WAGON-110) Support directory operations sanely.
[
http://jira.codehaus.org/browse/WAGON-110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter updated WAGON-110:
---
Fix Version/s: (was: 1.0-beta-3)
1.x
> Support directory operations sanely.
>
>
> Key: WAGON-110
> URL: http://jira.codehaus.org/browse/WAGON-110
> Project: Maven Wagon
> Issue Type: Improvement
> Components: wagon-provider-api
>Reporter: Luke Daley
> Fix For: 1.x
>
>
> The {{Wagon}} provider API is confused for directory operations. To simplify,
> I propose a new interface be created (e.g. {{DirectoryWagon}}) that wagons
> can implement...
> {code}
> bool isDirectory(String path) throws TransferFailedException,
> ResourceDoesNotExistException, AuthorizationException;
> String[] getFileList(String path) throws TransferFailedException,
> ResourceDoesNotExistException, AuthorizationException;
> void mkdir(String path) throws TransferFailedException,
> ResourceDoesNotExistException, AuthorizationException;
> void mkdirs(String path) throw throws TransferFailedException,
> ResourceDoesNotExistException, AuthorizationException;
> {code}
> This would also require removing all directory related methods from the
> {{Wagon}} interface. The {{AbstractWagon}} implementation could
> _transparently_ use the primitives from the {{DirectoryWagon}} interface (if
> implemented) to handle directory operations.
--
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
[jira] Created: (MAVENUPLOAD-2091) Please synchronize with http://m2repo.apithefire.org/ repository for release 0.1.1
Please synchronize with http://m2repo.apithefire.org/ repository for release 0.1.1 -- Key: MAVENUPLOAD-2091 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2091 Project: Maven Upload Requests Issue Type: Task Reporter: Chew Boon Aik "org.apithefire","[EMAIL PROTECTED]:/var/www/apithefire.org/m2repo","rsync_ssh","Chew Boon Aik","[EMAIL PROTECTED]",, -- 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
[jira] Created: (MPIR-103) Unable to find summary mojo
Unable to find summary mojo --- Key: MPIR-103 URL: http://jira.codehaus.org/browse/MPIR-103 Project: Maven 2.x Project Info Reports Plugin Issue Type: Bug Components: summary Affects Versions: 2.2 Reporter: Zach Legein Getting this error when running this snapshot Error getting reports from the plugin 'org.apache.maven.plugins:maven-project-info-reports-plugin': Unable to find the mojo 'org.apache.maven.plugins:maven-project-info-reports-plugin:2.2-SNAPSHOT:summary' in the plugin 'org.apache.maven.plugins:maven-project-info-reports-plugin' -- 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
[jira] Created: (MAVENUPLOAD-2092) Upload 20080530 Google Collection Library snapshot to central Maven repository
Upload 20080530 Google Collection Library snapshot to central Maven repository -- Key: MAVENUPLOAD-2092 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2092 Project: Maven Upload Requests Issue Type: Wish Reporter: Jared Levy Attachments: google-collect-snapshot-20080530-bundle.jar Please upload this bundle of the Google Collections Library to the central repository. http://google-collections.googlecode.com/files/google-collect-snapshot-20080530-bundle.jar Though the "snapshot" version is non-standard, it's consistent with our releases in http://code.google.com/p/google-collections/downloads/list?can=1&q=&colspec=Filename+Summary+Uploaded+Size+DownloadCount -- 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
[jira] Closed: (MCHECKSTYLE-96) Can we get a release of 2.2, is this ready?
[ http://jira.codehaus.org/browse/MCHECKSTYLE-96?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MCHECKSTYLE-96. Assignee: Benjamin Bentmann Resolution: Not A Bug The [release vote|http://www.nabble.com/-VOTE--Release-Maven-Checkstyle-plugin-version-2.2-to17580175.html] is already going on. > Can we get a release of 2.2, is this ready? > --- > > Key: MCHECKSTYLE-96 > URL: http://jira.codehaus.org/browse/MCHECKSTYLE-96 > Project: Maven 2.x Checkstyle Plugin > Issue Type: Wish >Affects Versions: 2.2 >Reporter: Zach Legein >Assignee: Benjamin Bentmann > -- 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
[jira] Reopened: (MSITE-332) Unable to load parent project from a relative path: Could not find the model file '/pom.xml'. for project unknown
[ http://jira.codehaus.org/browse/MSITE-332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Stevens reopened MSITE-332: --- Thanks Dennis, unfortunately the fix did not work; I saw the same error on the 31st after your patch, with the new snapshot jar. However, a different error is occurring this morning. This happens executing 'mvn site' from a brand new project created as follows: $ mvn archetype:create -DarchetypeGroupId=org.apache.maven.archetypes -DgroupId=test -DartifactId=test ... $ cd test $ mvn site ... [ERROR] BUILD ERROR [INFO] [INFO] Error getting reports from the plugin 'org.apache.maven.plugins:maven-project-info-reports-plugin': Unable to find the mojo 'org.apache.maven.plugins:maven-project-info-reports-plugin:2.2-SNAPSHOT:summary' in the plugin 'org.apache.maven.plugins:maven-project-info-reports-plugin' org/apache/maven/doxia/logging/Log [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Error getting reports from the plugin 'org.apache.maven.plugins:maven-project-info-reports-plugin': Unable to find the mojo 'org.apache.maven.plugins:maven-project-info-reports-plugin:2.2-SNAPSHOT:summary' in the plugin 'org.apache.maven.plugins:maven-project-info-reports-plugin' at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getReports(DefaultLifecycleExecutor.java:694) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getReports(DefaultLifecycleExecutor.java:642) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:517) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:280) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.PluginManagerException: Unable to find the mojo 'org.apache.maven.plugins:maven-project-info-reports-plugin:2.2-SNAPSHOT:summary' in the plugin 'org.apache.maven.plugins:maven-project-info-reports-plugin' at org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:571) at org.apache.maven.plugin.DefaultPluginManager.getReport(DefaultPluginManager.java:495) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getReports(DefaultLifecycleExecutor.java:683) ... 18 more Caused by: org.codehaus.plexus.component.repository.exception.ComponentLookupException: Unable to lookup component 'org.apache.maven.plugin.Mojoorg.apache.maven.plugins:maven-project-info-reports-plugin:2.2-SNAPSHOT:summary', it could not be started at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:339) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:440) at org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:562) ... 20 more Caused by: org.codehaus.plexus.component.repository.exception.ComponentLifecycleException: Error starting component at org.codehaus.plexus.component.manager.AbstractComponentManager.startComponentLifecycle(AbstractComponentManager.java:109) at org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance(AbstractComponentManager.java:95) at org.codehaus.plexus.component.manager.PerLookupComponentManager.getComponent(PerLookupComponentManager.java:48) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:331) ... 22 more Caused by: org.code
[jira] Commented: (MPIR-103) Unable to find summary mojo
[ http://jira.codehaus.org/browse/MPIR-103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=137114#action_137114 ] Zach Legein commented on MPIR-103: -- seems to be Caused by: java.lang.NoClassDefFoundError: org/apache/maven/doxia/logging/Log at java.lang.Class.getDeclaredConstructors0(Native Method) at java.lang.Class.privateGetDeclaredConstructors(Class.java:2389) at java.lang.Class.getConstructor0(Class.java:2699) at java.lang.Class.newInstance0(Class.java:326) at java.lang.Class.newInstance(Class.java:308) at org.codehaus.plexus.component.factory.java.JavaComponentFactory.newInstance(JavaComponentFactory.java:44) ... 34 more Caused by: java.lang.ClassNotFoundException: org.apache.maven.doxia.logging.Log at java.net.URLClassLoader$1.run(URLClassLoader.java:200) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at org.codehaus.classworlds.RealmClassLoader.loadClassDirect(RealmClassL > Unable to find summary mojo > --- > > Key: MPIR-103 > URL: http://jira.codehaus.org/browse/MPIR-103 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Bug > Components: summary >Affects Versions: 2.2 >Reporter: Zach Legein > > Getting this error when running this snapshot > Error getting reports from the plugin > 'org.apache.maven.plugins:maven-project-info-reports-plugin': Unable to find > the mojo > 'org.apache.maven.plugins:maven-project-info-reports-plugin:2.2-SNAPSHOT:summary' > in the plugin 'org.apache.maven.plugins:maven-project-info-reports-plugin' -- 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
[jira] Commented: (ARCHETYPE-135) add a variabl containing package in a path format
[ http://jira.codehaus.org/browse/ARCHETYPE-135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=137113#action_137113 ] Raphaël Piéroni commented on ARCHETYPE-135: --- I just rechecked, and there are tests that checks the feature in the archetype creation and the project generation. Can you please attach a test case to reproduce? > add a variabl containing package in a path format > - > > Key: ARCHETYPE-135 > URL: http://jira.codehaus.org/browse/ARCHETYPE-135 > Project: Maven Archetype > Issue Type: Improvement >Affects Versions: 2.0-alpha-2 >Reporter: Dominique Jean-Prost > > Actually, there is a variable "package" than can be used in the file during > generation. > It could be great if there was another variable than contained the package in > a path format. Example : > package = com.foo > packageInPathFormat=com/foo > This new variable could be used in resources path. -- 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
[jira] Commented: (ARCHETYPE-135) add a variabl containing package in a path format
[ http://jira.codehaus.org/browse/ARCHETYPE-135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=137123#action_137123 ] Raphaël Piéroni commented on ARCHETYPE-135: --- I just tested with jdk1.4.2 mvn2.0.9 and archetype-plugin 2.0-alpha-3 and it worked fine, even in a multi-module build. > add a variabl containing package in a path format > - > > Key: ARCHETYPE-135 > URL: http://jira.codehaus.org/browse/ARCHETYPE-135 > Project: Maven Archetype > Issue Type: Improvement >Affects Versions: 2.0-alpha-2 >Reporter: Dominique Jean-Prost > > Actually, there is a variable "package" than can be used in the file during > generation. > It could be great if there was another variable than contained the package in > a path format. Example : > package = com.foo > packageInPathFormat=com/foo > This new variable could be used in resources path. -- 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
[jira] Created: (MCHECKSTYLE-96) Can we get a release of 2.2, is this ready?
Can we get a release of 2.2, is this ready? --- Key: MCHECKSTYLE-96 URL: http://jira.codehaus.org/browse/MCHECKSTYLE-96 Project: Maven 2.x Checkstyle Plugin Issue Type: Wish Affects Versions: 2.2 Reporter: Zach Legein -- 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
[jira] Created: (MNG-3611) allow to pass in location of global settings file to maven cli
allow to pass in location of global settings file to maven cli -- Key: MNG-3611 URL: http://jira.codehaus.org/browse/MNG-3611 Project: Maven 2 Issue Type: New Feature Reporter: Eugene Kuleshov It would be useful to be able to pass in location of the global settings file (i.e. /conf/settings.xml) to MavenCli, similar how it is done for user's settings with -s command line option -- 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
[jira] Updated: (MJAVADOC-194) javadoc 2.4 does not [build-helper:add-source {execution: add-source}] when aggregating a javadoc for a project
[
http://jira.codehaus.org/browse/MJAVADOC-194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lois Modesitt updated MJAVADOC-194:
---
Attachment: m209out-UsingJavadoc2.5SNAPSHOT.txt
aggregated javadoc created BEFORE "build-helper:add-source" run on each module
involved in the aggregated javadoc. Therefore the source files included with
the "build-helper:add-source" is not included in the aggregated javadoc. Using
the command:
mvn javadoc:javadoc -Daggregate=true
> javadoc 2.4 does not [build-helper:add-source {execution: add-source}] when
> aggregating a javadoc for a project
> ---
>
> Key: MJAVADOC-194
> URL: http://jira.codehaus.org/browse/MJAVADOC-194
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 2.4
> Environment: Maven version: 2.0.9
> Java version: 1.5.0_12
> OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
>Reporter: Lois Modesitt
> Attachments: m209out-UsingJavadoc2.3.txt,
> m209out-UsingJavadoc2.4.txt, m209out-UsingJavadoc2.5SNAPSHOT.txt
>
>
> The javadoc does not include the "additional source" files defined using the
> "build-helper:add-source" in each of my subproject pom files when using
> javadoc plugin 2.4. The javadoc plugin 2.3 worked correctly.
> I use the "build-helper:add-source" to include additional source directories
> to the build. The additional source directories contain my generated source
> file. When I run the command using javadoc plugin version 2.4:
> mvn javadoc:javadoc -Daggregate=true
> (or have the aggregate=true specified inside of the pom) the
> "build-helper:add-source" is not run for each of the subprojects before the
> aggregated javadoc is created. Therefore the javadoc does not include the
> documentation for the files in the additional source directories.
> I also noted that the output for 2.3 javadoc plugin is:
> [INFO]task-segment: [javadoc:javadoc] (aggregator-style)
> but the output for the 2.4 javadoc plugin is:
> [INFO]task-segment: [javadoc:javadoc]
> I am not sure if the above output is changed between versions or if the
> "aggregator-style" is not detectd in the 2.4 version and has an influence in
> this issue.
> I have attached the log file for running my project using javadoc plugin
> version 2.3 and 2.4. Version 2.3 works and version 2.4 does not include the
> additional source files in the aggregated javadoc.
--
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
[jira] Issue Comment Edited: (MJAVADOC-194) javadoc 2.4 does not [build-helper:add-source {execution: add-source}] when aggregating a javadoc for a project
[
http://jira.codehaus.org/browse/MJAVADOC-194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=137129#action_137129
]
lois edited comment on MJAVADOC-194 at 6/2/08 3:15 PM:
aggregated javadoc created BEFORE "build-helper:add-source" run on each module
involved in the aggregated javadoc. Therefore the source files included with
the "build-helper:add-source" is not included in the aggregated javadoc. Using
the command:
mvn javadoc:javadoc -Daggregate=true
I used the 2.5-SNAPSHOT version of the maven-javadoc-plugin and this did not
fix the problem.
was (Author: lois):
aggregated javadoc created BEFORE "build-helper:add-source" run on each
module involved in the aggregated javadoc. Therefore the source files included
with the "build-helper:add-source" is not included in the aggregated javadoc.
Using the command:
mvn javadoc:javadoc -Daggregate=true
> javadoc 2.4 does not [build-helper:add-source {execution: add-source}] when
> aggregating a javadoc for a project
> ---
>
> Key: MJAVADOC-194
> URL: http://jira.codehaus.org/browse/MJAVADOC-194
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 2.4
> Environment: Maven version: 2.0.9
> Java version: 1.5.0_12
> OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
>Reporter: Lois Modesitt
> Attachments: m209out-UsingJavadoc2.3.txt,
> m209out-UsingJavadoc2.4.txt, m209out-UsingJavadoc2.5SNAPSHOT.txt
>
>
> The javadoc does not include the "additional source" files defined using the
> "build-helper:add-source" in each of my subproject pom files when using
> javadoc plugin 2.4. The javadoc plugin 2.3 worked correctly.
> I use the "build-helper:add-source" to include additional source directories
> to the build. The additional source directories contain my generated source
> file. When I run the command using javadoc plugin version 2.4:
> mvn javadoc:javadoc -Daggregate=true
> (or have the aggregate=true specified inside of the pom) the
> "build-helper:add-source" is not run for each of the subprojects before the
> aggregated javadoc is created. Therefore the javadoc does not include the
> documentation for the files in the additional source directories.
> I also noted that the output for 2.3 javadoc plugin is:
> [INFO]task-segment: [javadoc:javadoc] (aggregator-style)
> but the output for the 2.4 javadoc plugin is:
> [INFO]task-segment: [javadoc:javadoc]
> I am not sure if the above output is changed between versions or if the
> "aggregator-style" is not detectd in the 2.4 version and has an influence in
> this issue.
> I have attached the log file for running my project using javadoc plugin
> version 2.3 and 2.4. Version 2.3 works and version 2.4 does not include the
> additional source files in the aggregated javadoc.
--
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
[jira] Issue Comment Edited: (MJAVADOC-194) javadoc 2.4 does not [build-helper:add-source {execution: add-source}] when aggregating a javadoc for a project
[
http://jira.codehaus.org/browse/MJAVADOC-194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=137129#action_137129
]
lois edited comment on MJAVADOC-194 at 6/2/08 3:17 PM:
aggregated javadoc created BEFORE "build-helper:add-source" run on each module
involved in the aggregated javadoc. Therefore the source files included with
the "build-helper:add-source" is not included in the aggregated javadoc. Using
the command:
mvn javadoc:javadoc -Daggregate=true
I used the 2.5-SNAPSHOT version of the maven-javadoc-plugin and this did not
fix the problem.
The attached log files show the order of execution of the "javadoc" and the
"build-helper:add-source" for each module included in the project is different
between 2.3 (works) and 2.4/2.5-SNAPSHOT (does not work).
was (Author: lois):
aggregated javadoc created BEFORE "build-helper:add-source" run on each
module involved in the aggregated javadoc. Therefore the source files included
with the "build-helper:add-source" is not included in the aggregated javadoc.
Using the command:
mvn javadoc:javadoc -Daggregate=true
I used the 2.5-SNAPSHOT version of the maven-javadoc-plugin and this did not
fix the problem.
> javadoc 2.4 does not [build-helper:add-source {execution: add-source}] when
> aggregating a javadoc for a project
> ---
>
> Key: MJAVADOC-194
> URL: http://jira.codehaus.org/browse/MJAVADOC-194
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 2.4
> Environment: Maven version: 2.0.9
> Java version: 1.5.0_12
> OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
>Reporter: Lois Modesitt
> Attachments: m209out-UsingJavadoc2.3.txt,
> m209out-UsingJavadoc2.4.txt, m209out-UsingJavadoc2.5SNAPSHOT.txt
>
>
> The javadoc does not include the "additional source" files defined using the
> "build-helper:add-source" in each of my subproject pom files when using
> javadoc plugin 2.4. The javadoc plugin 2.3 worked correctly.
> I use the "build-helper:add-source" to include additional source directories
> to the build. The additional source directories contain my generated source
> file. When I run the command using javadoc plugin version 2.4:
> mvn javadoc:javadoc -Daggregate=true
> (or have the aggregate=true specified inside of the pom) the
> "build-helper:add-source" is not run for each of the subprojects before the
> aggregated javadoc is created. Therefore the javadoc does not include the
> documentation for the files in the additional source directories.
> I also noted that the output for 2.3 javadoc plugin is:
> [INFO]task-segment: [javadoc:javadoc] (aggregator-style)
> but the output for the 2.4 javadoc plugin is:
> [INFO]task-segment: [javadoc:javadoc]
> I am not sure if the above output is changed between versions or if the
> "aggregator-style" is not detectd in the 2.4 version and has an influence in
> this issue.
> I have attached the log file for running my project using javadoc plugin
> version 2.3 and 2.4. Version 2.3 works and version 2.4 does not include the
> additional source files in the aggregated javadoc.
--
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
[jira] Commented: (MCHECKSTYLE-96) Can we get a release of 2.2, is this ready?
[ http://jira.codehaus.org/browse/MCHECKSTYLE-96?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=137137#action_137137 ] Zach Legein commented on MCHECKSTYLE-96: Perfect timing, Its been in limbo for so long, i though it was forgotten. > Can we get a release of 2.2, is this ready? > --- > > Key: MCHECKSTYLE-96 > URL: http://jira.codehaus.org/browse/MCHECKSTYLE-96 > Project: Maven 2.x Checkstyle Plugin > Issue Type: Wish >Affects Versions: 2.2 >Reporter: Zach Legein >Assignee: Benjamin Bentmann > -- 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
[jira] Commented: (ARCHETYPE-178) omitting the package in the prompts leaves an unhelpful error message
[ http://jira.codehaus.org/browse/ARCHETYPE-178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=137138#action_137138 ] Raphaël Piéroni commented on ARCHETYPE-178: --- Is the following behaviour sufficient? mvn archetype:generate -DarchetypeCatalog=local [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'archetype'. [INFO] [INFO] Building Maven Default Project [INFO]task-segment: [archetype:generate] (aggregator-style) [INFO] [INFO] Preparing archetype:generate [INFO] No goals needed for project - skipping [INFO] [archetype:generate] [INFO] Generating project in Interactive mode [INFO] No archetype defined. Using maven-archetype-quickstart (org.apache.maven.archetypes:maven-archetype-quickstart:1.0) Choose archetype: 1: local -> gmaven-archetype-basic (GMaven Archetypes :: Basic) 2: local -> z (z) Choose a number: (1/2): 2 (ENTER) Define value for groupId: : (ENTER) Define value for artifactId: : a-r-t-i-f-a-c-t (ENTER) Define value for version: 1.0-SNAPSHOT: : (ENTER) Define value for package: : : (ENTER) [WARNING] Archetype is not fully configured Define value for groupId: : g.r.o.u.p (ENTER) Define value for package: g.r.o.u.p: : (ENTER) Confirm properties configuration: groupId: g.r.o.u.p artifactId: a-r-t-i-f-a-c-t version: 1.0-SNAPSHOT package: g.r.o.u.p Y: : > omitting the package in the prompts leaves an unhelpful error message > - > > Key: ARCHETYPE-178 > URL: http://jira.codehaus.org/browse/ARCHETYPE-178 > Project: Maven Archetype > Issue Type: Bug > Components: Generator >Affects Versions: 2.0-alpha-3 >Reporter: Brett Porter > > Define value for package: : > [INFO] > > [ERROR] BUILD FAILURE > [INFO] > > [INFO] : > org.apache.maven.archetype.exception.ArchetypeGenerationConfigurationFailure: > The archetype generation must be configured here > The archetype generation must be configured here > The archetype generation must be configured here > I believe > - the error message should be better, and prompt again > - the package should be defaulting to groupId? -- 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
[jira] Commented: (MSITE-332) Unable to load parent project from a relative path: Could not find the model file '/pom.xml'. for project unknown
[
http://jira.codehaus.org/browse/MSITE-332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=137143#action_137143
]
Dennis Lundberg commented on MSITE-332:
---
Michael,
Can you provide us with a sample project, including all POMs, that can be used
to reproduce the original issue. I'd like to get this issue fixed before we
release 2.0-beta-7.
The second error you get is coming from maven-project-info-reports-plugin. You
can get around that by specifying the version for that plugin in your pom, like
this:
{code:xml}
org.apache.maven.plugins
maven-project-info-reports-plugin
2.0.1
{code}
> Unable to load parent project from a relative path: Could not find the model
> file '/pom.xml'. for project unknown
> --
>
> Key: MSITE-332
> URL: http://jira.codehaus.org/browse/MSITE-332
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
> Components: site descriptor
>Affects Versions: 2.0-beta-7
>Reporter: Michael Stevens
>Assignee: Dennis Lundberg
> Fix For: 2.0-beta-7
>
>
> Execute site:site
> The plugin seems to look for a pom file in the directory above the project
> directory.
> This started occurring last night for us, using
> maven-site-plugin:2.0-beta-7-SNAPSHOT.
> Note that the project in question uses a parent POM, but does not specify a
> relative path.
> Here is the stack trace:
> [INFO] Unable to load parent project from a relative path: Could not find the
> model file 'c:\workdir\projects\pom.xml'. for project unknown
> [INFO] Parent project loaded from repository.
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] SiteToolException: Error reading default site descriptor:
> ${OUTPUTENCODING}
> [INFO]
>
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: SiteToolException:
> Error reading default site descriptor: ${OUTPUTENCODING}
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:564)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.plugin.MojoExecutionException: SiteToolException:
> Error reading default site descriptor: ${OUTPUTENCODING}
> at
> org.apache.maven.plugins.site.AbstractSiteRenderingMojo.createSiteRenderingContext(AbstractSiteRenderingMojo.java:230)
> at
> org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:113)
> at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:96)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
> ... 16 more
> Caused by: org.apache.maven.doxia.tools.SiteToolException: Error reading
> default site descriptor: ${OUTPUTENCODING}
> at
> org.apache.maven.doxia.tools.DefaultSiteTool.getDecorationModel(DefaultSiteTool.java:527)
> at
> org.apache.maven.plugins.site.AbstractSiteRenderingMojo.createSiteRenderingContext(AbstractSiteRenderingMojo.java:226)
[jira] Commented: (MPIR-103) Unable to find summary mojo
[ http://jira.codehaus.org/browse/MPIR-103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=137144#action_137144 ] Dennis Lundberg commented on MPIR-103: -- Bumping the maven prerequisites to 2.0.10-SNAPSHOT for this plugin should give the user a better error message. > Unable to find summary mojo > --- > > Key: MPIR-103 > URL: http://jira.codehaus.org/browse/MPIR-103 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Bug > Components: summary >Affects Versions: 2.2 >Reporter: Zach Legein > > Getting this error when running this snapshot > Error getting reports from the plugin > 'org.apache.maven.plugins:maven-project-info-reports-plugin': Unable to find > the mojo > 'org.apache.maven.plugins:maven-project-info-reports-plugin:2.2-SNAPSHOT:summary' > in the plugin 'org.apache.maven.plugins:maven-project-info-reports-plugin' -- 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
[jira] Closed: (MNG-3498) StringIndexOutOfBounds -1 during path translation while reading pom.xml
[
http://jira.codehaus.org/browse/MNG-3498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Casey closed MNG-3498.
---
Assignee: John Casey
Resolution: Fixed
Fix Version/s: 2.0.9
2.0.10
Fixed in 2.0.9 (see
http://www.nabble.com/-2.0.9-RC6--Release-Candidate-testing-to16435467.html#a16435467),
but forgot to close the issue. I'm marking fix version for both 2.0.9 and
2.0.10, to allow it to show up on the 2.0.10 changelog, since I just
re-verified that this fix is in place.
> StringIndexOutOfBounds -1 during path translation while reading pom.xml
> ---
>
> Key: MNG-3498
> URL: http://jira.codehaus.org/browse/MNG-3498
> Project: Maven 2
> Issue Type: Bug
> Components: Inheritance and Interpolation
>Affects Versions: 2.0.9, 2.1-alpha-1
>Reporter: John Casey
>Assignee: John Casey
> Fix For: 2.0.10, 2.0.9
>
>
> ${basedir} expresses this. The problem is that the
> DefaultPathTranslator expects there to be more than the simple basedir
> expression, and chokes if it encounters that expression as the only part of
> the value.
--
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
[jira] Commented: (MSITE-332) Unable to load parent project from a relative path: Could not find the model file '/pom.xml'. for project unknown
[
http://jira.codehaus.org/browse/MSITE-332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=137152#action_137152
]
Michael Stevens commented on MSITE-332:
---
Sorry, I'm unable to recreate the original error. I keep getting held up by the
NoClassDefFoundError on org/apache/maven/doxia/logging/Log, mentioned above,
even with maven-project-info-reports-plugin version 2.0. (That issue seems to
be tracked by MPIR-103.)
> Unable to load parent project from a relative path: Could not find the model
> file '/pom.xml'. for project unknown
> --
>
> Key: MSITE-332
> URL: http://jira.codehaus.org/browse/MSITE-332
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
> Components: site descriptor
>Affects Versions: 2.0-beta-7
>Reporter: Michael Stevens
>Assignee: Dennis Lundberg
> Fix For: 2.0-beta-7
>
>
> Execute site:site
> The plugin seems to look for a pom file in the directory above the project
> directory.
> This started occurring last night for us, using
> maven-site-plugin:2.0-beta-7-SNAPSHOT.
> Note that the project in question uses a parent POM, but does not specify a
> relative path.
> Here is the stack trace:
> [INFO] Unable to load parent project from a relative path: Could not find the
> model file 'c:\workdir\projects\pom.xml'. for project unknown
> [INFO] Parent project loaded from repository.
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] SiteToolException: Error reading default site descriptor:
> ${OUTPUTENCODING}
> [INFO]
>
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: SiteToolException:
> Error reading default site descriptor: ${OUTPUTENCODING}
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:564)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.plugin.MojoExecutionException: SiteToolException:
> Error reading default site descriptor: ${OUTPUTENCODING}
> at
> org.apache.maven.plugins.site.AbstractSiteRenderingMojo.createSiteRenderingContext(AbstractSiteRenderingMojo.java:230)
> at
> org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:113)
> at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:96)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
> ... 16 more
> Caused by: org.apache.maven.doxia.tools.SiteToolException: Error reading
> default site descriptor: ${OUTPUTENCODING}
> at
> org.apache.maven.doxia.tools.DefaultSiteTool.getDecorationModel(DefaultSiteTool.java:527)
> at
> org.apache.maven.plugins.site.AbstractSiteRenderingMojo.createSiteRenderingContext(AbstractSiteRenderingMojo.java:226)
> ... 20 more
> Caused by: java.io.UnsupportedEncodingException: ${OUTPUTENCODING}
> at sun.io.Converters.getConverterClass(Converters.java:218)
> at sun.io.Converters.newConverter(Converters.java:251)
>
[jira] Commented: (MJAVADOC-194) javadoc 2.4 does not [build-helper:add-source {execution: add-source}] when aggregating a javadoc for a project
[
http://jira.codehaus.org/browse/MJAVADOC-194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=137154#action_137154
]
Vincent Siveton commented on MJAVADOC-194:
--
Sorry, but I am not sure to understand correctly your usecase: could you send
us a test case?
> javadoc 2.4 does not [build-helper:add-source {execution: add-source}] when
> aggregating a javadoc for a project
> ---
>
> Key: MJAVADOC-194
> URL: http://jira.codehaus.org/browse/MJAVADOC-194
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 2.4
> Environment: Maven version: 2.0.9
> Java version: 1.5.0_12
> OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
>Reporter: Lois Modesitt
> Attachments: m209out-UsingJavadoc2.3.txt,
> m209out-UsingJavadoc2.4.txt, m209out-UsingJavadoc2.5SNAPSHOT.txt
>
>
> The javadoc does not include the "additional source" files defined using the
> "build-helper:add-source" in each of my subproject pom files when using
> javadoc plugin 2.4. The javadoc plugin 2.3 worked correctly.
> I use the "build-helper:add-source" to include additional source directories
> to the build. The additional source directories contain my generated source
> file. When I run the command using javadoc plugin version 2.4:
> mvn javadoc:javadoc -Daggregate=true
> (or have the aggregate=true specified inside of the pom) the
> "build-helper:add-source" is not run for each of the subprojects before the
> aggregated javadoc is created. Therefore the javadoc does not include the
> documentation for the files in the additional source directories.
> I also noted that the output for 2.3 javadoc plugin is:
> [INFO]task-segment: [javadoc:javadoc] (aggregator-style)
> but the output for the 2.4 javadoc plugin is:
> [INFO]task-segment: [javadoc:javadoc]
> I am not sure if the above output is changed between versions or if the
> "aggregator-style" is not detectd in the 2.4 version and has an influence in
> this issue.
> I have attached the log file for running my project using javadoc plugin
> version 2.3 and 2.4. Version 2.3 works and version 2.4 does not include the
> additional source files in the aggregated javadoc.
--
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
[jira] Commented: (ARCHETYPE-178) omitting the package in the prompts leaves an unhelpful error message
[ http://jira.codehaus.org/browse/ARCHETYPE-178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=137155#action_137155 ] Brett Porter commented on ARCHETYPE-178: yep > omitting the package in the prompts leaves an unhelpful error message > - > > Key: ARCHETYPE-178 > URL: http://jira.codehaus.org/browse/ARCHETYPE-178 > Project: Maven Archetype > Issue Type: Bug > Components: Generator >Affects Versions: 2.0-alpha-3 >Reporter: Brett Porter > > Define value for package: : > [INFO] > > [ERROR] BUILD FAILURE > [INFO] > > [INFO] : > org.apache.maven.archetype.exception.ArchetypeGenerationConfigurationFailure: > The archetype generation must be configured here > The archetype generation must be configured here > The archetype generation must be configured here > I believe > - the error message should be better, and prompt again > - the package should be defaulting to groupId? -- 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
[jira] Created: (SCM-382) cleanup dependencies in maven-scm-provider-accurev
cleanup dependencies in maven-scm-provider-accurev
--
Key: SCM-382
URL: http://jira.codehaus.org/browse/SCM-382
Project: Maven SCM
Issue Type: Bug
Reporter: Eugene Kuleshov
scm provider for Accurew has some dependencies unusual for scm providers. Those
need to be replaced with plexus-utils
{code}
org.codehaus.plexus
plexus-cli
1.4
commons-lang
commons-lang
2.4
{code}
--
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
[jira] Closed: (MAVENUPLOAD-2071) rsync_ssh request for seleniumdsl.sourceforge.net
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2071. --- Resolution: Fixed > rsync_ssh request for seleniumdsl.sourceforge.net > - > > Key: MAVENUPLOAD-2071 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2071 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Cauê Haucke Porta Guerra >Assignee: Carlos Sanchez > > "net.sf.seleniumdsl","[EMAIL > PROTECTED]:/home/groups/s/se/seleniumdsl/htdocs/m2repo","rsync_ssh","Caue > Guerra","[EMAIL PROTECTED]",, > Project page generated by maven hosted at project domain: > http://seleniumdsl.sourceforge.net/team-list.html -- 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
[jira] Closed: (MAVENUPLOAD-2087) rsync_ssh delete for caelum-stella.sourceforge.net
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2087. --- Assignee: Carlos Sanchez Resolution: Fixed > rsync_ssh delete for caelum-stella.sourceforge.net > -- > > Key: MAVENUPLOAD-2087 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2087 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Cauê Haucke Porta Guerra >Assignee: Carlos Sanchez > > Could you please delete the following repo: > "net.sf.caelum-stella","[EMAIL > PROTECTED]:/home/groups/c/ca/caelum-stella/htdocs/maven","rsync_ssh","Caue > Guerra","[EMAIL PROTECTED]",, > thanks -- 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
[jira] Commented: (MAVENUPLOAD-2090) rsync-ssh request for yusuke.homeip.net
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=137157#action_137157 ] Carlos Sanchez commented on MAVENUPLOAD-2090: - the groupId should be reversed "net.homeip.yusuke" > rsync-ssh request for yusuke.homeip.net > --- > > Key: MAVENUPLOAD-2090 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2090 > Project: Maven Upload Requests > Issue Type: Task >Reporter: Yusuke Yamamoto > > Hi, > I want you guys to add my repository to the automatic setup. > "yusuke.homeip.net","[EMAIL > PROTECTED]:/Users/mavensync/maven2","rsync_ssh","Yusuke Yamamoto","[EMAIL > PROTECTED]",, > This domain is hosting the "Twitter4J" project. It's a dyndns domain and no > whois info is available. > http://yusuke.homeip.net/twitter4j/en/index.html > You can verify that I'm the owner of the project by checking the project > mailing list. > http://yusuke.homeip.net/twitter4j/en/index.html#mailingList > http://groups.google.com/group/twitter4j/browse_thread/thread/d742d816e7ecf7a6 > Or the license term or the project. > http://yusuke.homeip.net/twitter4j/en/index.html#license > Thanks, > Yusuke -- 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
[jira] Closed: (MAVENUPLOAD-2091) Please synchronize with http://m2repo.apithefire.org/ repository for release 0.1.1
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2091. --- Assignee: Carlos Sanchez Resolution: Fixed > Please synchronize with http://m2repo.apithefire.org/ repository for release > 0.1.1 > -- > > Key: MAVENUPLOAD-2091 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2091 > Project: Maven Upload Requests > Issue Type: Task >Reporter: Chew Boon Aik >Assignee: Carlos Sanchez > > "org.apithefire","[EMAIL > PROTECTED]:/var/www/apithefire.org/m2repo","rsync_ssh","Chew Boon > Aik","[EMAIL PROTECTED]",, -- 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
[jira] Updated: (SCM-382) cleanup dependencies in maven-scm-provider-accurev
[
http://jira.codehaus.org/browse/SCM-382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eugene Kuleshov updated SCM-382:
Attachment: accurev.patch
proposed changes. verified that tck tests pass with these changes
> cleanup dependencies in maven-scm-provider-accurev
> --
>
> Key: SCM-382
> URL: http://jira.codehaus.org/browse/SCM-382
> Project: Maven SCM
> Issue Type: Bug
>Reporter: Eugene Kuleshov
> Attachments: accurev.patch
>
>
> scm provider for Accurew has some dependencies unusual for scm providers.
> Those need to be replaced with plexus-utils
> {code}
>
> org.codehaus.plexus
> plexus-cli
> 1.4
>
>
> commons-lang
> commons-lang
> 2.4
>
> {code}
--
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
[jira] Commented: (MAVENUPLOAD-2090) rsync-ssh request for yusuke.homeip.net
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=137159#action_137159 ] Yusuke Yamamoto commented on MAVENUPLOAD-2090: -- Sorry to put you to the trouble. The groupid has been corrected. http://yusuke.homeip.net/maven2/net/homeip/yusuke/twitter4j/ Thanks, Yusuke > rsync-ssh request for yusuke.homeip.net > --- > > Key: MAVENUPLOAD-2090 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2090 > Project: Maven Upload Requests > Issue Type: Task >Reporter: Yusuke Yamamoto > > Hi, > I want you guys to add my repository to the automatic setup. > "yusuke.homeip.net","[EMAIL > PROTECTED]:/Users/mavensync/maven2","rsync_ssh","Yusuke Yamamoto","[EMAIL > PROTECTED]",, > This domain is hosting the "Twitter4J" project. It's a dyndns domain and no > whois info is available. > http://yusuke.homeip.net/twitter4j/en/index.html > You can verify that I'm the owner of the project by checking the project > mailing list. > http://yusuke.homeip.net/twitter4j/en/index.html#mailingList > http://groups.google.com/group/twitter4j/browse_thread/thread/d742d816e7ecf7a6 > Or the license term or the project. > http://yusuke.homeip.net/twitter4j/en/index.html#license > Thanks, > Yusuke -- 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
[jira] Commented: (MNG-2433) Maven looks for snapshots in offline mode
[ http://jira.codehaus.org/browse/MNG-2433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=137168#action_137168 ] Jose M Beas commented on MNG-2433: -- We have the same problem here. We are migrating from an old environment (with direct connection to the central repositories) to a new one that uses artifactory to proxy all the repositories. We were using Maven 2.0.7 in the old environment and Maven 2.0.8 in the new one. By the way, all the default plugins appear in: http://svn.apache.org/viewvc/maven/components/tags/maven-2.0.9/maven-project/src/main/resources/org/apache/maven/project/pom-4.0.0.xml?view=markup but not in http://svn.apache.org/viewvc/maven/components/tags/maven-2.0.8/maven-project/src/main/resources/org/apache/maven/project/pom-4.0.0.xml?view=markup Please, reopen the bug. Best regards, JMB > Maven looks for snapshots in offline mode > - > > Key: MNG-2433 > URL: http://jira.codehaus.org/browse/MNG-2433 > Project: Maven 2 > Issue Type: Bug > Components: Dependencies >Affects Versions: 2.0.5 >Reporter: Carsten Ziegeler >Assignee: Jason van Zyl >Priority: Critical > Fix For: 2.0.6 > > > It seems that sometimes Maven2 is looking for snapshots in offline mode (this > happens for example in the Cocoon project). here is an output that might help: > :\dev\workspace\cocoon-2.2\core\cocoon-webapp>mvn -o -Dmaven.test.skip=true > coc > oon:deploy > [INFO] > NOTE: Maven is executing in offline mode. Any artifacts not already in your > loca > l > repository will be inaccessible. > [INFO] Scanning for projects... > [INFO] Searching repository for plugin with prefix: 'cocoon'. > [INFO] org.apache.maven.plugins: checking for updates from snapshots > [INFO] org.apache.maven.plugins: checking for updates from mortbay-repo > [INFO] org.codehaus.mojo: checking for updates from snapshots > [INFO] org.codehaus.mojo: checking for updates from mortbay-repo > [INFO] snapshot org.apache.cocoon:cocoon-deployer-plugin:1.0.0-SNAPSHOT: > checkin > g for updates from snapshots > [INFO] snapshot org.apache.cocoon:cocoon-deployer-plugin:1.0.0-SNAPSHOT: > checkin > g for updates from mortbay-repo > [INFO] snapshot org.apache.cocoon:cocoon-deployer-plugin:1.0.0-SNAPSHOT: > checkin > g for updates from central > [INFO] snapshot org.apache.cocoon:cocoon-deployer-plugin:1.0.0-SNAPSHOT: > checkin > g for updates from apache.snapshot > [INFO] snapshot org.apache.cocoon:cocoon-deployer-plugin:1.0.0-SNAPSHOT: > checkin > g for updates from apache-cvs > [INFO] snapshot org.apache.cocoon:cocoon-deployer-plugin:1.0.0-SNAPSHOT: > checkin > g for updates from apache.snapshots > [INFO] snapshot org.apache.cocoon:cocoon-deployer:1-SNAPSHOT: checking for > updat > es from snapshots > [INFO] snapshot org.apache.cocoon:cocoon-deployer:1-SNAPSHOT: checking for > updat > es from mortbay-repo > [INFO] snapshot org.apache.cocoon:cocoon-deployer:1-SNAPSHOT: checking for > updat > es from central > [INFO] snapshot org.apache.cocoon:cocoon-deployer:1-SNAPSHOT: checking for > updat > es from apache.snapshot > [INFO] snapshot org.apache.cocoon:cocoon-deployer:1-SNAPSHOT: checking for > updat > es from apache-cvs > [INFO] snapshot org.apache.cocoon:cocoon-deployer:1-SNAPSHOT: checking for > updat > es from apache.snapshots > [INFO] snapshot org.apache.cocoon:cocoon-tools-modules:1-SNAPSHOT: checking > for > updates from snapshots > [INFO] snapshot org.apache.cocoon:cocoon-tools-modules:1-SNAPSHOT: checking > for > updates from mortbay-repo > [INFO] snapshot org.apache.cocoon:cocoon-tools-modules:1-SNAPSHOT: checking > for > updates from central > [INFO] snapshot org.apache.cocoon:cocoon-tools-modules:1-SNAPSHOT: checking > for > updates from apache.snapshot > [INFO] snapshot org.apache.cocoon:cocoon-tools-modules:1-SNAPSHOT: checking > for > updates from apache-cvs > [INFO] snapshot org.apache.cocoon:cocoon-tools-modules:1-SNAPSHOT: checking > for > updates from apache.snapshots > [INFO] snapshot org.apache.cocoon:cocoon:1-SNAPSHOT: checking for updates > from s > napshots > [INFO] snapshot org.apache.cocoon:cocoon:1-SNAPSHOT: checking for updates > from m > ortbay-repo > [INFO] snapshot org.apache.cocoon:cocoon:1-SNAPSHOT: checking for updates > from c > entral > [INFO] snapshot org.apache.cocoon:cocoon:1-SNAPSHOT: checking for updates > from a > pache.snapshot > [INFO] snapshot org.apache.cocoon:cocoon:1-SNAPSHOT: checking for updates > from a > pache-cvs > [INFO] snapshot org.apache.cocoon:cocoon:1-SNAPSHOT: checking for updates > from a > pache.snapshots -- 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.
[jira] Commented: (ARCHETYPE-135) add a variabl containing package in a path format
[ http://jira.codehaus.org/browse/ARCHETYPE-135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=137171#action_137171 ] Dominique Jean-Prost commented on ARCHETYPE-135: Well, there are times when you really feel ashamed. I've checked once again, and it's ok. Apologies for reopening this case. Thank you for the feature. > add a variabl containing package in a path format > - > > Key: ARCHETYPE-135 > URL: http://jira.codehaus.org/browse/ARCHETYPE-135 > Project: Maven Archetype > Issue Type: Improvement >Affects Versions: 2.0-alpha-2 >Reporter: Dominique Jean-Prost > > Actually, there is a variable "package" than can be used in the file during > generation. > It could be great if there was another variable than contained the package in > a path format. Example : > package = com.foo > packageInPathFormat=com/foo > This new variable could be used in resources path. -- 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
