[jira] Updated: (MRM-347) Undefined ${appserver.home} and ${appserver.base}
[
http://jira.codehaus.org/browse/MRM-347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wendy Smoak updated MRM-347:
Affects Version/s: 1.0-alpha-2
> Undefined ${appserver.home} and ${appserver.base}
> -
>
> Key: MRM-347
> URL: http://jira.codehaus.org/browse/MRM-347
> Project: Archiva
> Issue Type: Bug
>Affects Versions: 1.0-alpha-1, 1.0-alpha-2
> Environment: Windows, Maven 2.0.6, JDK 5 or JDK 6
>Reporter: Jan Nielsen
> Fix For: 1.0.x
>
>
> When I run:
> mvn jetty:run
> from trunk at r538691, the "appserver.base" property is undefined, resulting
> in the creation of this directory:
> Directory of C:\dev\apache-maven\archiva\archiva-web\archiva-webapp
> 05/17/2007 02:24 PM ${appserver.base}
> 05/16/2007 11:40 AM 14,681 pom.xml
> 05/16/2007 11:40 AM src
> 05/17/2007 11:06 AM target
--
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: (SUREFIRE-343) html escaping problems in xml reports
html escaping problems in xml reports
-
Key: SUREFIRE-343
URL: http://jira.codehaus.org/browse/SUREFIRE-343
Project: Maven Surefire
Issue Type: Bug
Components: xml generation
Affects Versions: 2.0 (2.2 plugin)
Reporter: Brydie McCoy
Priority: Minor
Hi,
I'm having some problems with the escaping of html specific characters (namely
the < and >) in the surefire reports.
The following example test:
{code}
public void testShouldFail() throws Exception
{
fail(" This Failed ");
}
{code}
resulted in the following xml report
{code}
junit.framework.AssertionFailedError: &html&&body&&h2&
This Failed &/h2&&/body&&/html&
at junit.framework.Assert.fail(Assert.java:47)
at FailingTest.testShouldFail(FailingTest.java:7)
{code}
The text in the "message' attribute has been correctly escaped but the text
within the tags seems to just have & for any of the html
characters.
--
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: (MRM-416) Find artifact does not work.
[ http://jira.codehaus.org/browse/MRM-416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wendy Smoak updated MRM-416: Fix Version/s: (was: 1.0.x) 1.0-alpha-2 Based on the date this was resolved and svn history, it must be included in1.0-alpha-2. > Find artifact does not work. > > > Key: MRM-416 > URL: http://jira.codehaus.org/browse/MRM-416 > Project: Archiva > Issue Type: Bug >Affects Versions: 1.0-alpha-2 >Reporter: Henry S. Isidro >Assignee: Maria Odea Ching > Fix For: 1.0-alpha-2 > > > Finding an artifact always shows the 'No results found' message even though > the artifact that is being looked for is in the repository. -- 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: (MRM-399) NPE trying to access an artifact that should be proxied
[
http://jira.codehaus.org/browse/MRM-399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wendy Smoak closed MRM-399.
---
Assignee: Wendy Smoak
Resolution: Fixed
Fix Version/s: (was: 1.0.x)
1.0-alpha-2
A request for
http://localhost:8080/archiva/repository/internal/org/apache/maven/maven-core/2.0.6/maven-core-2.0.6.jar
works fine for me in1.0-alpha-2.
INFO | jvm 1| 2007/06/24 18:15:36 | [INFO] The appserver server has been
initialized.
INFO | jvm 1| 2007/06/24 18:15:36 | [INFO] The appserver server has
started.
INFO | jvm 1| 2007/06/24 18:15:57 | 2007-06-24 18:15:56,984
[SocketListener0-1] DEBUG
org.apache.maven.archiva.proxy.RepositoryProxyConnectors:default - Attempting
connector: ProxyConnector[
INFO | jvm 1| 2007/06/24 18:15:57 |
source:ArchivaRepository[internal,file://${appserver.home}/repositories/internal]
INFO | jvm 1| 2007/06/24 18:15:57 |
target:ArchivaRepository[maven2-repository.dev.java.net,http://download.java.net/maven/2/]
INFO | jvm 1| 2007/06/24 18:15:57 | proxyId:
INFO | jvm 1| 2007/06/24 18:15:57 | policy[releases]:once
INFO | jvm 1| 2007/06/24 18:15:57 | policy[checksum]:fix
INFO | jvm 1| 2007/06/24 18:15:57 | policy[snapshots]:disabled
INFO | jvm 1| 2007/06/24 18:15:57 | policy[cache-failures]:cache
INFO | jvm 1| 2007/06/24 18:15:57 | ]
INFO | jvm 1| 2007/06/24 18:15:57 | 2007-06-24 18:15:56,984
[SocketListener0-1] DEBUG
org.apache.maven.archiva.proxy.RepositoryProxyConnectors:default - Using
target repository: maven2-repository.dev.java.net - layout: default -
targetPath: org/apache/maven/maven-core/2.0.6/maven-core-2.0.6.jar
INFO | jvm 1| 2007/06/24 18:15:57 | 2007-06-24 18:15:56,984
[SocketListener0-1] DEBUG
org.apache.maven.archiva.proxy.RepositoryProxyConnectors:default - Applying
[releases] policy with [once]
INFO | jvm 1| 2007/06/24 18:15:57 | 2007-06-24 18:15:56,984
[SocketListener0-1] DEBUG
org.apache.maven.archiva.policies.PreDownloadPolicy:releases - OK to update
releases, local file does not exist.
INFO | jvm 1| 2007/06/24 18:15:57 | 2007-06-24 18:15:56,984
[SocketListener0-1] DEBUG
org.apache.maven.archiva.proxy.RepositoryProxyConnectors:default - Applying
[snapshots] policy with [disabled]
INFO | jvm 1| 2007/06/24 18:15:57 | 2007-06-24 18:15:56,984
[SocketListener0-1] DEBUG
org.apache.maven.archiva.policies.PreDownloadPolicy:snapshots - OK to update,
snapshot policy does not apply for non-snapshot versions.
INFO | jvm 1| 2007/06/24 18:15:57 | 2007-06-24 18:15:56,984
[SocketListener0-1] DEBUG
org.apache.maven.archiva.proxy.RepositoryProxyConnectors:default - Applying
[cache-failures] policy with [cache]
INFO | jvm 1| 2007/06/24 18:15:57 | 2007-06-24 18:15:56,984
[SocketListener0-1] ERROR
org.apache.maven.archiva.policies.PreDownloadPolicy:cache-failures - Unknown
checksum policyCode [cache]
INFO | jvm 1| 2007/06/24 18:15:57 | 2007-06-24 18:15:56,984
[SocketListener0-1] DEBUG
org.apache.maven.archiva.proxy.RepositoryProxyConnectors:default - Didn't pass
the [cache-failures] policy.
INFO | jvm 1| 2007/06/24 18:15:57 | 2007-06-24 18:15:56,984
[SocketListener0-1] INFO
org.apache.maven.archiva.proxy.RepositoryProxyConnectors:default - Failed
pre-download policies -
C:\${appserver.home}\repositories\internal\org\apache\maven\maven-core\2.0.6\maven-core-2.0.6.jar
INFO | jvm 1| 2007/06/24 18:15:57 | 2007-06-24 18:15:56,984
[SocketListener0-1] DEBUG
org.apache.maven.archiva.proxy.RepositoryProxyConnectors:default - Attempting
connector: ProxyConnector[
INFO | jvm 1| 2007/06/24 18:15:57 |
source:ArchivaRepository[internal,file://${appserver.home}/repositories/internal]
INFO | jvm 1| 2007/06/24 18:15:57 |
target:ArchivaRepository[central,http://repo1.maven.org/maven2]
INFO | jvm 1| 2007/06/24 18:15:57 | proxyId:null
INFO | jvm 1| 2007/06/24 18:15:57 | policy[releases]:once
INFO | jvm 1| 2007/06/24 18:15:57 | policy[checksum]:fix
INFO | jvm 1| 2007/06/24 18:15:57 | policy[snapshots]:disabled
INFO | jvm 1| 2007/06/24 18:15:57 | policy[cache-failures]:cached
INFO | jvm 1| 2007/06/24 18:15:57 | ]
INFO | jvm 1| 2007/06/24 18:15:57 | 2007-06-24 18:15:56,984
[SocketListener0-1] DEBUG
org.apache.maven.archiva.proxy.RepositoryProxyConnectors:default - Using
target repository: central - layout: default - targetPath:
org/apache/maven/maven-core/2.0.6/maven-core-2.0.6.jar
INFO | jvm 1| 2007/06/24 18:15:57 | 2007-06-24 18:15:56,984
[SocketListener0-1] DEBUG
org.apache.maven.archiva.proxy.RepositoryProxyConnectors:default - Applying
[releases] policy with [once]
INFO | jvm 1| 2007/06/24 18:15:57 | 2007-06-24 18:15:56,984
[SocketListener0-1] DEBUG
org.apache.maven.archiva.policies.PreDownloadPolicy:releases - OK to u
[jira] Closed: (MRM-416) Find artifact does not work.
[ http://jira.codehaus.org/browse/MRM-416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching closed MRM-416. Resolution: Fixed > Find artifact does not work. > > > Key: MRM-416 > URL: http://jira.codehaus.org/browse/MRM-416 > Project: Archiva > Issue Type: Bug >Affects Versions: 1.0-alpha-2 >Reporter: Henry S. Isidro >Assignee: Maria Odea Ching > Fix For: 1.0.x > > > Finding an artifact always shows the 'No results found' message even though > the artifact that is being looked for is in the repository. -- 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-128) Plugin does not accept URL to an offlineLink's location
[ http://jira.codehaus.org/browse/MJAVADOC-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Libor Kramolis updated MJAVADOC-128: Attachment: MJAVADOC-128.diff This is simple patch against tag maven-javadoc-plugin-2.2. > Plugin does not accept URL to an offlineLink's location > --- > > Key: MJAVADOC-128 > URL: http://jira.codehaus.org/browse/MJAVADOC-128 > Project: Maven 2.x Javadoc Plugin > Issue Type: Bug >Affects Versions: 2.2 >Reporter: Greg Thompson > Attachments: MJAVADOC-128.diff > > > According to > http://java.sun.com/j2se/1.4.2/docs/tooldocs/solaris/javadoc.html#linkoffline, > the location "is the path or URL to the directory containing the > package-list file for the external documentation." The plugin's > OfflineLink.java uses a java.io.File for the argument, which munges it if > it's a URL. Easiest fix might be to just use String instead of File. -- 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: (MEV-531) ant:ant:1.6.5 (completly wrong dependencies)
ant:ant:1.6.5 (completly wrong dependencies) Key: MEV-531 URL: http://jira.codehaus.org/browse/MEV-531 Project: Maven Evangelism Issue Type: Bug Components: Dependencies Reporter: Piotr Tabor Current ant:ant pom is: 4.0.0 ant ant 1.6.5 xerces *xerces-impl* 2.6.2 true xml-apis xml-apis *2.6.2* true Instead of: xerces-impl should be xercesImpl (xerces-impl does not exist in repo) And the version of xml-apis should be: 1.3.04 (2.6.2 does not exist) -- 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: (MANTTASKS-72) Remove hardcoded groupId in install-provider task
[ http://jira.codehaus.org/browse/MANTTASKS-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MANTTASKS-72. -- Resolution: Fixed > Remove hardcoded groupId in install-provider task > - > > Key: MANTTASKS-72 > URL: http://jira.codehaus.org/browse/MANTTASKS-72 > Project: Maven 2.x Ant Tasks > Issue Type: Improvement > Components: install-provider task >Affects Versions: 2.0.6 >Reporter: Ben Hale > Fix For: 2.0.7 > > Attachments: InstallWagonProviderTask.java.patch, > MANTTASKS-72_site.diff > > > Currently, the InstallWagonProviderTask hard-codes the 'WAGON_GROUP_ID' value > internally with no way to override it. Because of this, it is impossible to > use a custom wagon that does not have a groupId of 'org.apache.maven.wagon' > to upload files with a deploy task. > It would be better if the install-provider task used that value as a default > (so that it would be specified in the common case), but had a groupId setter > allowing it to overriden. -- 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: (MANTTASKS-18) filesetId does not contain all dependencies when artifact was not yet locally installed
[ http://jira.codehaus.org/browse/MANTTASKS-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MANTTASKS-18. -- Resolution: Fixed > filesetId does not contain all dependencies when artifact was not yet locally > installed > --- > > Key: MANTTASKS-18 > URL: http://jira.codehaus.org/browse/MANTTASKS-18 > Project: Maven 2.x Ant Tasks > Issue Type: Bug > Components: dependencies task >Affects Versions: 2.0.6 > Environment: java version "1.4.2_04", Linux 2.6.11.12, Apache Ant > version 1.6.5 >Reporter: Ingo Weichsel >Priority: Critical > Fix For: 2.0.7 > > Attachments: MANTTASKS-18_new.diff, MANTTASKS-18_new.tgz, > MANTTASKS-18_new2.diff, patch.txt > > > In the artifact:dependencies task the filesetId is only correctly set, when > the artifact was installed locally before running ant. > After deletion of the local repository the dependant artifacts will be > downloaded to the local repository, but only one of two dependant files will > be included in the ant fileset. The classpath is set correctly. > After running "mvn install" locally for the "as-base-launcher" maven project, > ant computes the correct filesetId. > The ant-project depends on the artifact "as-base-launcher" which itselfs > depends only on classworlds. Snippets from ant buildfiles, poms and ant > output follows: > From the ant buildfile: > > > > pathId="as-launcher.classpath" verbose="true"> > > > > > > > > > > > > > > > > > The referenced POM defining the ant dependencies: > > 4.0.0 > actis > ant-as-base > 1.0-SNAPSHOT > > > actis > as-base-launcher > 1.0-SNAPSHOT > > > > > actisRepository > actisRepository > http://company.com:/repository/ > > > > Output of the ant run: > launcherJAR: > actis:ant-as-base:jar:1.0-SNAPSHOT (selected) > actis:as-base-launcher:jar:1.0-SNAPSHOT (selected) > classworlds:classworlds:jar:1.1-alpha-1 (selected) > [echo] CLASSPATH: > /home/iwe/.m2/repository/classworlds/classworlds/1.1-alpha-1/classworlds-1.1-alpha-1.jar:/home/iwe/.m2/repository/actis/as-base-launcher/1.0-20051103.102305-8/as-base-launcher-1.0-20051103.102305-8.jar > [echo] FILESET: > /home/iwe/.m2/repository/classworlds/classworlds/1.1-alpha-1/classworlds-1.1-alpha-1.jar -- 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-1609) Synchronize opensymphony:xwork:jar:2.0.3 to central repo
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100449 ] Rainer Hermanns commented on MAVENUPLOAD-1609: -- Carlos, The OpenSymphony repo should be cleaned up now. I removed all of the snapshots and manually recreated the maven-metadata.xml(.md5/sha1) files. Please let me know, if any other changes are required. tia, Rainer > Synchronize opensymphony:xwork:jar:2.0.3 to central repo > > > Key: MAVENUPLOAD-1609 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1609 > Project: maven-upload-requests > Issue Type: Bug >Reporter: Olivier Lamy > > Hi, > The artifact opensymphony:xwork:jar:2.0.3 is in the opensymphony repository > http://maven2.opensymphony.com/opensymphony/xwork/2.0.3/ . > Is it possible to have in http://repo1.maven.org/maven2/opensymphony/xwork/ ? > 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: (MNG-1916) Making it possible for plug-in to add modules to the reactor programatically
[
http://jira.codehaus.org/browse/MNG-1916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100446
]
Nils Fredrik Gjerull commented on MNG-1916:
---
I am actually speaking about two different kinds of plug-ins one is the maven
plug-in, the other kind of plug-in is the Java Plug-in Framework (JPF) plug-in.
Your are right in writing that JPF plug-ins is the same as a maven module. A
bit confusing use of terms there.
What I wanted to do was to have one master module and several sub-modules.
First the sub-modules would be built, the maven life-cycle would run until the
package phase. In the integration-test phase all the sub-modules should be
moved into the target directory of the master module. The essence is that a JPF
program need a number of sub-modules to be able to run. It need a bootstrap
module and a set of core JPF plug-ins.
Is there a way to make the master module run the build process for every
sub-module until the package phase and then take over the control?
> Making it possible for plug-in to add modules to the reactor programatically
>
>
> Key: MNG-1916
> URL: http://jira.codehaus.org/browse/MNG-1916
> Project: Maven 2
> Issue Type: Improvement
> Components: Plugin API, Reactor and workspace
>Reporter: Nils Fredrik Gjerull
> Fix For: 2.1.x
>
>
> I would like to be able to specify a number of directories as plug-in
> directories, automatically discover every plug-in in those directories and
> include them in the reactor. As I understands it the reactor with it's
> modules ({{org.apache.maven.execution.ReactorManager}}) is created in
> {{org.apache.maven.DefaultMaven}}. If I understands this correctly maven
> plug-ins can't add projects to the reactor programatically.
> My proposition to solve this is to add a phase which will be executed after
> the pom.xml is parsed, but before the information stored in
> Model/MavenProject is used, and most importantly before the {{ReactorManager
> is created}}. Then you can add information to the MavenProject
> programatically, increasing the flexibility for plug-ins.
> I am not fluent in the maven2 code base, but it seems to me that this require
> quite a lot of changes to the code. As I understands it the life cycle starts
> after the {{ReactorManager}} is made, and therefore after the information in
> Model have started to be used.
--
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
