[jira] Work started: (MRM-385) Maven config docs refer to /proxy urls
[ http://jira.codehaus.org/browse/MRM-385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on MRM-385 started by Maria Odea Ching. > Maven config docs refer to /proxy urls > -- > > Key: MRM-385 > URL: http://jira.codehaus.org/browse/MRM-385 > Project: Archiva > Issue Type: Improvement > Components: documentation >Reporter: Wendy Smoak >Assignee: Maria Odea Ching >Priority: Critical > Fix For: 1.0-beta-2 > > > The Maven Configuration page still refers to urls containing "/proxy". These > no longer exist. > http://maven.apache.org/archiva/guides/maven-configuration.html > Also incorporate info from: > http://docs.codehaus.org/display/MAVENUSER/Archiva+as+a+Proxy -- 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-438) broken images in the download box on the artifact page
[ http://jira.codehaus.org/browse/MRM-438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching closed MRM-438. Resolution: Fixed Fixed in -r575191 - Leveraged existing jar and pom images (size is 24x24) - Set background of the download-type icons to tranparent - Updated site.css > broken images in the download box on the artifact page > -- > > Key: MRM-438 > URL: http://jira.codehaus.org/browse/MRM-438 > Project: Archiva > Issue Type: Bug >Affects Versions: 1.0-beta-1 >Reporter: Brett Porter >Assignee: Maria Odea Ching > Fix For: 1.0-beta-2 > > Attachments: firefox-download.png, IE-download.png > > > these don't appear to work at all in the latest version - it isn't noticeable > in firefox but in ie you get the big white square with an X in it. -- 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-435) need to review repository defaults
[ http://jira.codehaus.org/browse/MRM-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MRM-435: - Assignee: (was: Brett Porter) > need to review repository defaults > -- > > Key: MRM-435 > URL: http://jira.codehaus.org/browse/MRM-435 > Project: Archiva > Issue Type: Bug >Affects Versions: 1.0-beta-1 >Reporter: Brett Porter > Fix For: 1.0-beta-2 > > > we should review the use of the appserver path as the default location, as it > is not particularly friendly to seting up as a standalone web application. I > believe there is insufficient error handling to correct this situation if the > user forgets to first set the variables during installation. -- 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-437) admin editing of proxy connectors fails in multiple instances
[ http://jira.codehaus.org/browse/MRM-437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MRM-437: - Assignee: (was: Brett Porter) > admin editing of proxy connectors fails in multiple instances > - > > Key: MRM-437 > URL: http://jira.codehaus.org/browse/MRM-437 > Project: Archiva > Issue Type: Bug >Affects Versions: 1.0-beta-1 >Reporter: Brett Porter > Fix For: 1.0-beta-2 > > > I've seen the following: > - edit first one and save (order changes) > - edit new first one and save (end up with the same connector for both, eg > the blacklist is duplicated) > - in other circumstances, I'd seen editing the proxy connector produce a > second one > - removing the corresponding remote repository doesn't remove the associated > network proxy. > I believe this entire set of actions needs a review. -- 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-398) configure guest access by default for pre-configured repositories
[ http://jira.codehaus.org/browse/MRM-398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MRM-398: - Assignee: (was: Brett Porter) > configure guest access by default for pre-configured repositories > - > > Key: MRM-398 > URL: http://jira.codehaus.org/browse/MRM-398 > Project: Archiva > Issue Type: Bug > Components: Users/Security >Affects Versions: 1.0-alpha-1 >Reporter: Brett Porter > Fix For: 1.0-beta-2 > > > I think it makes sense for repositories to be readable by guests by default > for a good OOTB experience. -- 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: (MNG-3099) Profiles ignored when working with non-projects (such as archetype:create)
[
http://jira.codehaus.org/browse/MNG-3099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107214
]
William Ferguson edited comment on MNG-3099 at 9/13/07 12:57 AM:
-
Invoking a Mojo that doesn't require a project (ie [EMAIL PROTECTED] false* in
your Mojo) doesn't load the Profiles defined in LOCAL_HOME settings or
MAVEN_HOME settings.
In an effort to make this issue as explicit as possible, I have attached
Plugin-showing-MNG3099.zip
It contains a plugin project (with a Mojo conigured with [EMAIL PROTECTED]
false*) and local and global settings files.
Put the local and global settings files in the normal place and build and
install the plugin.
Then from the plugin project folder execute:
{quote}
D:\Modules\maven-test-plugin>mvn
com.yarris.maven.plugins:maven-test-plugin:profile-props
[INFO] Scanning for projects...
[INFO] snapshot com.yarris.maven.plugins:maven-test-plugin:1.0-SNAPSHOT:
checking for updates from snapshot
[INFO]
[INFO] Building maven-test-plugin
[INFO]task-segment:
[com.yarris.maven.plugins:maven-test-plugin:profile-props] (aggregator-style)
[INFO]
[INFO] [test:profile-props]
[INFO] local-profile-prop=local-profile-prop-value
[INFO] global-profile-prop=global-profile-prop-value
[INFO]
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 1 second
[INFO] Finished at: Thu Sep 13 15:47:18 EST 2007
[INFO] Final Memory: 2M/4M
[INFO]
{quote}
Note that the local-profile-prop and global-profile-prop have resolved to the
expected values.
Now execute:
{quote}
D:\Modules\maven-test-plugin>mvn
com.yarris.maven.plugins:maven-test-plugin:profile-props -f no-pom.xml
[INFO] Scanning for projects...
[INFO]
[INFO] Building Maven Default Project
[INFO]task-segment:
[com.yarris.maven.plugins:maven-test-plugin:profile-props] (aggregator-style)
[INFO]
[INFO] [test:profile-props]
[INFO] local-profile-prop=null
[INFO] global-profile-prop=null
[INFO]
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 1 second
[INFO] Finished at: Thu Sep 13 15:48:56 EST 2007
[INFO] Final Memory: 2M/4M
[INFO]
{quote}
Note how local-profile-prop and global-profile-prop no longer have values.
As has been noted the most common example of this is archetype:create which
requires the remote repository to be explicitly provided on the command line
via the remoteRepositories System property if you are pulling an archetype from
somewhere other than central. Eg
{code}
mvn archetype:create -DgroupId=com.yarris -DartifactId=foo-project
-DarchetypeGroupId=com.yarris.maven.archetype \
-DarchetypeArtifactId=archetype-standard
-DremoteRepositories=http://somewhere.com.au:8080/proximity/repository/release
{code}
It should be possible to define an active Profile in either local or global
settings.xml that defines a remote repository, and have the archetype pulled
from that repository.
It should also be possible to refer to a property provided by an active Profile
But it occurs for any Mojo that does not require a project.
was:
Invoking a Mojo that doesn't require a project (ie [EMAIL PROTECTED] false* in
your Mojo) doesn't load the Profiles defined in LOCAL_HOME settings or
MAVEN_HOME settings.
In an effort to make this issue as explicit as possible, I have attached
Plugin-showing-MNG3099.zip
It contains a plugin project (with a Mojo conigured with *requiresProject
false*) and local and global settings files.
Put the local and global settings files in the normal place and build and
install the plugin.
Then from the plugin project folder execute:
{code}
D:\Modules\maven-test-plugin>mvn
com.yarris.maven.plugins:maven-test-plugin:profile-props
[INFO] Scanning for projects...
[INFO] snapshot com.yarris.maven.plugins:maven-test-plugin:1.0-SNAPSHOT:
checking for updates from snapshot
[INFO]
[INFO] Building maven-test-plugin
[INFO]task-segment:
[com.yarris.maven.plugins:maven-test-plugin:profile-props] (aggregator-style)
[INFO]
[INFO] [test:profile-props]
[INFO] local-profile-prop=local-profile-prop-value
[INFO] globa
[jira] Closed: (MRM-496) adding a proxy connector action is not working after repository changes
[ http://jira.codehaus.org/browse/MRM-496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed MRM-496. Resolution: Fixed > adding a proxy connector action is not working after repository changes > --- > > Key: MRM-496 > URL: http://jira.codehaus.org/browse/MRM-496 > Project: Archiva > Issue Type: Bug > Components: web application >Affects Versions: 1.0-beta-2 >Reporter: Brett Porter >Assignee: Brett Porter > Fix For: 1.0-beta-2 > > > need to write tests also, and run through the related issues for proxy > connector admin in JIRA -- 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-3099) Profiles ignored when working with non-projects (such as archetype:create)
[
http://jira.codehaus.org/browse/MNG-3099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Ferguson updated MNG-3099:
--
Attachment: Plugin-showing-MNG3099.zip
Invoking a Mojo that doesn't require a project (ie [EMAIL PROTECTED] false* in
your Mojo) doesn't load the Profiles defined in LOCAL_HOME settings or
MAVEN_HOME settings.
In an effort to make this issue as explicit as possible, I have attached
Plugin-showing-MNG3099.zip
It contains a plugin project (with a Mojo conigured with *requiresProject
false*) and local and global settings files.
Put the local and global settings files in the normal place and build and
install the plugin.
Then from the plugin project folder execute:
{code}
D:\Modules\maven-test-plugin>mvn
com.yarris.maven.plugins:maven-test-plugin:profile-props
[INFO] Scanning for projects...
[INFO] snapshot com.yarris.maven.plugins:maven-test-plugin:1.0-SNAPSHOT:
checking for updates from snapshot
[INFO]
[INFO] Building maven-test-plugin
[INFO]task-segment:
[com.yarris.maven.plugins:maven-test-plugin:profile-props] (aggregator-style)
[INFO]
[INFO] [test:profile-props]
[INFO] local-profile-prop=local-profile-prop-value
[INFO] global-profile-prop=global-profile-prop-value
[INFO]
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 1 second
[INFO] Finished at: Thu Sep 13 15:47:18 EST 2007
[INFO] Final Memory: 2M/4M
[INFO]
{code}
Note that the local-profile-prop and global-profile-prop have resolved to the
expected values.
Now execute:
{code}
D:\Modules\maven-test-plugin>mvn
com.yarris.maven.plugins:maven-test-plugin:profile-props -f no-pom.xml
[INFO] Scanning for projects...
[INFO]
[INFO] Building Maven Default Project
[INFO]task-segment:
[com.yarris.maven.plugins:maven-test-plugin:profile-props] (aggregator-style)
[INFO]
[INFO] [test:profile-props]
[INFO] local-profile-prop=null
[INFO] global-profile-prop=null
[INFO]
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 1 second
[INFO] Finished at: Thu Sep 13 15:48:56 EST 2007
[INFO] Final Memory: 2M/4M
[INFO]
{code}
Note how local-profile-prop and global-profile-prop no longer have values.
As has been noted the most common example of this is archetype:create which
requires the remote repository to be explicitly provided on the command line
via the remoteRepositories System property if you are pulling an archetype from
somewhere other than central. Eg
{code}
mvn archetype:create -DgroupId=com.yarris -DartifactId=foo-project
-DarchetypeGroupId=com.yarris.maven.archetype \
-DarchetypeArtifactId=archetype-standard
-DremoteRepositories=http://somewhere.com.au:8080/proximity/repository/release
{code}
It should be possible to define an active Profile in either local or global
settings.xml that defines a remote repository, and have the archetype pulled
from that repository.
It should also be possible to refer to a property provided by an active Profile
But it occurs for any Mojo that does not require a project.
> Profiles ignored when working with non-projects (such as archetype:create)
> --
>
> Key: MNG-3099
> URL: http://jira.codehaus.org/browse/MNG-3099
> Project: Maven 2
> Issue Type: Bug
>Reporter: Joakim Erdfelt
>Assignee: John Casey
>Priority: Blocker
> Fix For: 2.1
>
> Attachments: MNG-2261-2.patch, MNG-2261.patch,
> Plugin-showing-MNG3099.zip
>
>
> Several conditions have to be met to show this bug.
> 1) Be in an environment that does not have access to repo1.maven.org, (such
> as a corporate environment)
> 2) Have no content in your local repository (a fresh install of maven 2.0.4)
> 3) Attempt to use a plugin that has no project requirement (such as
> archetype:create)
> The plugin fails because access to repo1.maven.org cannot be accessed.
> Recommended solution:
> Create a settings.xml profile that changes the location of the 'central'
> repository to point to an internal resource (such as a maven-proxy
> installation).
>
>
>
> use_internal
>
>
> central
> Internal
[jira] Commented: (MIDEA-105) Allow modules to be grouped by parent artifactId
[ http://jira.codehaus.org/browse/MIDEA-105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107211 ] Jason Dillon commented on MIDEA-105: This patch is similar in concept to MIDEA-105, but instead of using relative paths, uses the artifactId of parent modules to group modules. > Allow modules to be grouped by parent artifactId > > > Key: MIDEA-105 > URL: http://jira.codehaus.org/browse/MIDEA-105 > Project: Maven 2.x IDEA Plugin > Issue Type: New Feature >Affects Versions: 2.2 >Reporter: Jason Dillon > Attachments: MIDEA-105.diff > > -- 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: (MIDEA-105) Allow modules to be grouped by parent artifactId
Allow modules to be grouped by parent artifactId Key: MIDEA-105 URL: http://jira.codehaus.org/browse/MIDEA-105 Project: Maven 2.x IDEA Plugin Issue Type: New Feature Affects Versions: 2.2 Reporter: Jason Dillon Attachments: MIDEA-105.diff -- 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: (MIDEA-105) Allow modules to be grouped by parent artifactId
[ http://jira.codehaus.org/browse/MIDEA-105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Dillon updated MIDEA-105: --- Attachment: MIDEA-105.diff > Allow modules to be grouped by parent artifactId > > > Key: MIDEA-105 > URL: http://jira.codehaus.org/browse/MIDEA-105 > Project: Maven 2.x IDEA Plugin > Issue Type: New Feature >Affects Versions: 2.2 >Reporter: Jason Dillon > Attachments: MIDEA-105.diff > > -- 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: (NMAVEN-41) Configuration of Remote Services through the IDE
[ http://jira.codehaus.org/browse/NMAVEN-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107210 ] Shane Isbell commented on NMAVEN-41: Fixed and in trunk. (VS2005 only). > Configuration of Remote Services through the IDE > > > Key: NMAVEN-41 > URL: http://jira.codehaus.org/browse/NMAVEN-41 > Project: NMaven > Issue Type: New Feature > Environment: Visual Studio, Sharp Develop >Reporter: Shane Isbell > > The developer will be able to add/delete remote/local repository access > through the IDE. This action would modify the repository tag in the pom.xml > and is also used in conjunction with NMaven-39, where the developer can then > add a dependency from the repo to the project. > This feature also includes the ability to change which MavenEmbedder to use > for the IDE. -- 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: (NMAVEN-39) Browse Maven Repository and Add/Delete Dependencies through the IDE
[ http://jira.codehaus.org/browse/NMAVEN-39?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107209 ] Shane Isbell commented on NMAVEN-39: Fixed and in trunk. (VS2005 only). > Browse Maven Repository and Add/Delete Dependencies through the IDE > --- > > Key: NMAVEN-39 > URL: http://jira.codehaus.org/browse/NMAVEN-39 > Project: NMaven > Issue Type: New Feature > Environment: Windows, Linux, Visual Studio, Sharp Develop >Reporter: Shane Isbell > > The developer should be able to browse local and remote repositories and > attach/delete dependencies (including transitive) to both the IDE project > file and the pom.xml. -- 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-460) invalid cache policy
[ http://jira.codehaus.org/browse/MRM-460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MRM-460: - Assignee: Brett Porter Fix Version/s: 1.0-beta-2 > invalid cache policy > > > Key: MRM-460 > URL: http://jira.codehaus.org/browse/MRM-460 > Project: Archiva > Issue Type: Bug > Components: remote proxy >Affects Versions: 1.0-beta-2 >Reporter: nicolas de loof >Assignee: Brett Porter > Fix For: 1.0-beta-2 > > Attachments: cache.patch, typo.patch > > > CachedFailuresPolicy has a log typo when the requested policy is not supported > "Unknown **checksum** policyCode" > attached Patch to be applied on archiva-policies. -- 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: (MAVENUPLOAD-1693) Upload truezip
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Asankha Perera reopened MAVENUPLOAD-1693: - >scm url is wrong, has to be the url to the source repository Sorry for the delay.. but I have updated the upload archive as requested here http://people.apache.org/~asankha/temp/truezip-upload.jar >why de.schlichtherle.io groupId and not net.java.dev.truezip This is out of my control and the author has used "de.schlichtherle.io" as the actual package in the source code, and I believe thats what is more relevant here > Upload truezip > -- > > Key: MAVENUPLOAD-1693 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1693 > Project: maven-upload-requests > Issue Type: Bug >Reporter: Asankha Perera >Assignee: Carlos Sanchez > > http://people.apache.org/~asankha/temp/truezip-upload.jar > https://truezip.dev.java.net/ > TrueZIP is a Java based Virtual File System (VFS) which enables client > applications to access ZIP, TAR and derivative archive types transparently as > if they were just directories in a file's path name. -- 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-2788) Anchor tags on POM amd Settings reference pages are broken in Firefox
[ http://jira.codehaus.org/browse/MNG-2788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MNG-2788. Resolution: Fixed Site deployed. > Anchor tags on POM amd Settings reference pages are broken in Firefox > - > > Key: MNG-2788 > URL: http://jira.codehaus.org/browse/MNG-2788 > Project: Maven 2 > Issue Type: Bug > Components: Documentation: General >Affects Versions: 2.0.4 > Environment: Firefox 2.0.0.1 on Windows XP SP2. >Reporter: Ryan Breidenbach >Assignee: Dennis Lundberg >Priority: Trivial > Fix For: Documentation Deficit > > Attachments: pom.html.diff > > > The TOC anchors at the top of the POM and Settings Reference pages do not > work in Firefox. It appears that all of the anchor links are capitalized > while the anchor labels are all lower case. Also, some of the links contain > spaces while the labels contain underscores. This is causing the links to > fail in Firefox. > http://maven.apache.org/pom.html > http://maven.apache.org/settings.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: (MNG-3074) Anchor links in several documentations do not work
[ http://jira.codehaus.org/browse/MNG-3074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MNG-3074. Resolution: Fixed Fix Version/s: Documentation Deficit Site deployed. > Anchor links in several documentations do not work > -- > > Key: MNG-3074 > URL: http://jira.codehaus.org/browse/MNG-3074 > Project: Maven 2 > Issue Type: Bug > Components: Documentation: General >Reporter: Rick Janda >Assignee: Dennis Lundberg >Priority: Minor > Fix For: Documentation Deficit > > > In the online documentation User Centre, the anchor links from the table of > contents at the beginning of the Settings Reference and the POM Reference do > not work at all. Also the anchor links to the different sections at the > beginning of the Getting Started Guide do not work. -- 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] Work started: (MRM-496) adding a proxy connector action is not working after repository changes
[ http://jira.codehaus.org/browse/MRM-496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on MRM-496 started by Brett Porter. > adding a proxy connector action is not working after repository changes > --- > > Key: MRM-496 > URL: http://jira.codehaus.org/browse/MRM-496 > Project: Archiva > Issue Type: Bug > Components: web application >Affects Versions: 1.0-beta-2 >Reporter: Brett Porter >Assignee: Brett Porter > Fix For: 1.0-beta-2 > > > need to write tests also, and run through the related issues for proxy > connector admin in JIRA -- 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: (CONTINUUM-1443) Add an 'Always build' checkbox in 'build definition'
[ http://jira.codehaus.org/browse/CONTINUUM-1443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed CONTINUUM-1443. --- Resolution: Fixed svn rev 575112. > Add an 'Always build' checkbox in 'build definition' > > > Key: CONTINUUM-1443 > URL: http://jira.codehaus.org/browse/CONTINUUM-1443 > Project: Continuum > Issue Type: Improvement > Components: Core system >Affects Versions: 1.1-beta-2 > Environment: all >Reporter: Arnaud Doucet >Assignee: Olivier Lamy >Priority: Minor > Fix For: 1.1-beta-3 > > > On 'build definition' screen split 'build fresh' checkbox in 2 checkbox : > 'New check out' and 'Always build' -- 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: (MSITE-200) Schedule and release doxia 1.0-alpha-9
[ http://jira.codehaus.org/browse/MSITE-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MSITE-200. - Resolution: Fixed Doxia is released. > Schedule and release doxia 1.0-alpha-9 > -- > > Key: MSITE-200 > URL: http://jira.codehaus.org/browse/MSITE-200 > Project: Maven 2.x Site Plugin > Issue Type: Task > Components: doxia integration >Affects Versions: 2.0-beta-5 >Reporter: Jason van Zyl >Assignee: Dennis Lundberg > Fix For: 2.0-beta-6 > > -- 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-3184) Doxia Release 1.0-alpha-9
[ http://jira.codehaus.org/browse/MNG-3184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MNG-3184. Resolution: Fixed Doxia is released. > Doxia Release 1.0-alpha-9 > - > > Key: MNG-3184 > URL: http://jira.codehaus.org/browse/MNG-3184 > Project: Maven 2 > Issue Type: Task >Affects Versions: 2.1-alpha-1 >Reporter: Jason van Zyl >Assignee: Dennis Lundberg > Fix For: 2.1-alpha-1 > > -- 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: (CONTINUUM-1278) Need to add description and/or name to build defintion
[ http://jira.codehaus.org/browse/CONTINUUM-1278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed CONTINUUM-1278. --- Assignee: Olivier Lamy Resolution: Fixed a description field added to solved CONTINUUM-1427. > Need to add description and/or name to build defintion > -- > > Key: CONTINUUM-1278 > URL: http://jira.codehaus.org/browse/CONTINUUM-1278 > Project: Continuum > Issue Type: Improvement >Affects Versions: 1.1-alpha-1 >Reporter: Paul Spencer >Assignee: Olivier Lamy > Fix For: 1.1-beta-3 > > > When their are several "Build definition"s for a project, it can be difficult > to know why each exists. This can be eliminated by adding an name and/or > description of the "Build Definition". The name and description must be > optional, or at least defaultes, to minimize the effort required when adding > a project or build. > As an example the MyFaces Tomahawk project has many "Build Definition" for > some of their projects. In those cases each "Build Definition" builds > against a different implementation of the JSF standard. -- 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: (CONTINUUM-1278) Need to add description and/or name to build defintion
[ http://jira.codehaus.org/browse/CONTINUUM-1278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated CONTINUUM-1278: Fix Version/s: (was: Future) 1.1-beta-3 > Need to add description and/or name to build defintion > -- > > Key: CONTINUUM-1278 > URL: http://jira.codehaus.org/browse/CONTINUUM-1278 > Project: Continuum > Issue Type: Improvement >Affects Versions: 1.1-alpha-1 >Reporter: Paul Spencer > Fix For: 1.1-beta-3 > > > When their are several "Build definition"s for a project, it can be difficult > to know why each exists. This can be eliminated by adding an name and/or > description of the "Build Definition". The name and description must be > optional, or at least defaultes, to minimize the effort required when adding > a project or build. > As an example the MyFaces Tomahawk project has many "Build Definition" for > some of their projects. In those cases each "Build Definition" builds > against a different implementation of the JSF standard. -- 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-1713) Upload grails-maven-plugin 0.1
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arnaud Heritier closed MAVENUPLOAD-1713. Resolution: Won't Fix Due to issues reported by carlos (external repositories references forbidden, non-public dependencies in grails poms) I'll fix our poms in a version 0.2. > Upload grails-maven-plugin 0.1 > -- > > Key: MAVENUPLOAD-1713 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1713 > Project: maven-upload-requests > Issue Type: Task >Reporter: Arnaud Heritier > Attachments: grails-0.5.6-base-0.1-bundle.jar, > grails-0.5.6-launch-0.1-bundle.jar, grails-0.5.6-poms-0.1-bundle.jar, > grails-0.5.6-web-0.1-bundle.jar > > > The parent pom is also needed : > http://forge.octo.com/downloads/mtg-0.1-bundle.jar > The Grails plugin for maven is a set of goals to easily develop a Grails > application using maven 2. > 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: (MJAR-30) Allow inludes/excludes definition
[ http://jira.codehaus.org/browse/MJAR-30?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107185 ] Dennis Lundberg commented on MJAR-30: - Alex, the patch has not been reviewed or applied yet. You will have to download the plugin sources from svn and apply the patch yourself, for the time being. > Allow inludes/excludes definition > - > > Key: MJAR-30 > URL: http://jira.codehaus.org/browse/MJAR-30 > Project: Maven 2.x Jar Plugin > Issue Type: Improvement >Reporter: Michael Böckling > Attachments: MJAR-30-maven-jar-plugin-1.patch, > MJAR-30-maven-jar-plugin.patch, mjar-30.patch > > > Allow the definition of includes / excludes, so the Jars content can be > customized. -- 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-1713) Upload grails-maven-plugin 0.1
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107184 ] Arnaud Heritier commented on MAVENUPLOAD-1713: -- For plugin repositories I though about them after the release :-( But for repositories I need some of them (3rd party @ octo, spring repositories) because grails uses some non public artifacts and I'm not sure that it's a good idea to updload them . WDYT ? > Upload grails-maven-plugin 0.1 > -- > > Key: MAVENUPLOAD-1713 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1713 > Project: maven-upload-requests > Issue Type: Task >Reporter: Arnaud Heritier > Attachments: grails-0.5.6-base-0.1-bundle.jar, > grails-0.5.6-launch-0.1-bundle.jar, grails-0.5.6-poms-0.1-bundle.jar, > grails-0.5.6-web-0.1-bundle.jar > > > The parent pom is also needed : > http://forge.octo.com/downloads/mtg-0.1-bundle.jar > The Grails plugin for maven is a set of goals to easily develop a Grails > application using maven 2. > 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] Closed: (MAVENUPLOAD-1693) Upload truezip
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1693. --- Assignee: Carlos Sanchez Resolution: Incomplete > Upload truezip > -- > > Key: MAVENUPLOAD-1693 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1693 > Project: maven-upload-requests > Issue Type: Bug >Reporter: Asankha Perera >Assignee: Carlos Sanchez > > http://people.apache.org/~asankha/temp/truezip-upload.jar > https://truezip.dev.java.net/ > TrueZIP is a Java based Virtual File System (VFS) which enables client > applications to access ZIP, TAR and derivative archive types transparently as > if they were just directories in a file's path name. -- 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-1713) Upload grails-maven-plugin 0.1
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107183 ] Carlos Sanchez commented on MAVENUPLOAD-1713: - you need to remove the repositories and pluginRepositories sections > Upload grails-maven-plugin 0.1 > -- > > Key: MAVENUPLOAD-1713 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1713 > Project: maven-upload-requests > Issue Type: Task >Reporter: Arnaud Heritier > Attachments: grails-0.5.6-base-0.1-bundle.jar, > grails-0.5.6-launch-0.1-bundle.jar, grails-0.5.6-poms-0.1-bundle.jar, > grails-0.5.6-web-0.1-bundle.jar > > > The parent pom is also needed : > http://forge.octo.com/downloads/mtg-0.1-bundle.jar > The Grails plugin for maven is a set of goals to easily develop a Grails > application using maven 2. > 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: (MJAR-30) Allow inludes/excludes definition
[ http://jira.codehaus.org/browse/MJAR-30?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107182 ] Alex Deschapelles commented on MJAR-30: --- This might not be the right spot for this comment, but... This bug has been killing me. Where can I get a snaphot of the plugin with this patch, or the source with the patch so I can build it myself. I looked in the snapshot repositories and did not see one. Thanks > Allow inludes/excludes definition > - > > Key: MJAR-30 > URL: http://jira.codehaus.org/browse/MJAR-30 > Project: Maven 2.x Jar Plugin > Issue Type: Improvement >Reporter: Michael Böckling > Attachments: MJAR-30-maven-jar-plugin-1.patch, > MJAR-30-maven-jar-plugin.patch, mjar-30.patch > > > Allow the definition of includes / excludes, so the Jars content can be > customized. -- 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: (CONTINUUM-1445) Impossible to add two projects with the same name even if they have differents version and/or scmUrl
[ http://jira.codehaus.org/browse/CONTINUUM-1445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed CONTINUUM-1445. --- Resolution: Fixed svn rev 575063 > Impossible to add two projects with the same name even if they have > differents version and/or scmUrl > > > Key: CONTINUUM-1445 > URL: http://jira.codehaus.org/browse/CONTINUUM-1445 > Project: Continuum > Issue Type: Bug > Components: Core system, Web - UI >Affects Versions: 1.1-beta-2 >Reporter: Olivier Lamy >Assignee: Olivier Lamy > Fix For: 1.1-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] Closed: (CONTINUUM-1038) Build definitions should list what type they are (ant, maven, maven2, shell)
[ http://jira.codehaus.org/browse/CONTINUUM-1038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed CONTINUUM-1038. --- Resolution: Fixed svn rev 575063 > Build definitions should list what type they are (ant, maven, maven2, shell) > > > Key: CONTINUUM-1038 > URL: http://jira.codehaus.org/browse/CONTINUUM-1038 > Project: Continuum > Issue Type: Bug > Components: Web - UI >Affects Versions: 1.1-alpha-1 >Reporter: Brett Porter >Assignee: Olivier Lamy > Fix For: 1.1-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: (MEV-546) Ant 1.6.5 has groupId 'ant', Ant 1.7.0 has groupId 'org.apache.ant', needs "relocation"
Ant 1.6.5 has groupId 'ant', Ant 1.7.0 has groupId 'org.apache.ant', needs "relocation" --- Key: MEV-546 URL: http://jira.codehaus.org/browse/MEV-546 Project: Maven Evangelism Issue Type: Bug Components: Relocation Reporter: Brian Topping Ant 1.6.5 has groupId 'ant', Ant 1.7.0 has groupId 'org.apache.ant', and it doesn't appear that the project has been properly relocated. I'm having an issue with a local dependency on 1.6.5 (which should establish the desired version with a "nearer" resolution) and the difference in groupId causing 1.7.0 to be imported transitively. -- 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: (MWAR-116) The outputFileNameMapping config creates bad dependency files in WEB-INF/lib
[
http://jira.codehaus.org/browse/MWAR-116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107176
]
Stephane Nicoll commented on MWAR-116:
--
maven 2.1-beta-1 does ot exist :)
I've tried myself with maven 2.0.4 to 2.0.7 so it's something unrelated. I 've
feedback from the dev list. I'll check later
> The outputFileNameMapping config creates bad dependency files in WEB-INF/lib
>
>
> Key: MWAR-116
> URL: http://jira.codehaus.org/browse/MWAR-116
> Project: Maven 2.x War Plugin
> Issue Type: Bug
>Affects Versions: 2.1-alpha-1
>Reporter: Chris Moesel
>Assignee: Stephane Nicoll
> Attachments: mwar_93_webapp.zip
>
>
> I've tried using the new outputFileNameMapping feature (MWAR-93) by adding
> the following to my POM:
>
> org.apache.maven.plugins
> maven-war-plugin
> 2.1-alpha-1-SNAPSHOT
>
> ${artifactId}.${extension}
>
>
> This results in really oddly named files in my web-inf/lib now. A typical
> example:
> org.springframework-mywebapp.null
> So, the resulting files are really mapped more like: ${groupId of the
> dependency}-${artifactId of my war module}.null
> I've attached an example Maven 2 project that demonstrates this. Just run
> "mvn package" and look at the result in 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] Updated: (MNG-3206) Changes to MavenSettingsBuilder breaks backward compatibility
[
http://jira.codehaus.org/browse/MNG-3206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Casey updated MNG-3206:
Description:
When I tried to run a the component-it-plugin from maven sandbox during an
integration-test run on the assembly plugin with a Maven build from Sept. 10,
2007, I got the following:
Exception in thread "main" java.lang.NoSuchMethodError:
org.apache.maven.settings.MavenSettingsBuilder.buildSettings()Lorg/apache/maven/settings/Settings;
at
org.apache.maven.shared.test.plugin.RepositoryTool.findLocalRepositoryDirectory(RepositoryTool.java:100)
at
org.apache.maven.shared.test.plugin.ProjectTool.manglePomForTesting(ProjectTool.java:301)
at
org.apache.maven.shared.test.plugin.ProjectTool.packageProjectArtifact(ProjectTool.java:168)
at
org.apache.maven.shared.test.plugin.ComponentTestTool.prepareForTesting(ComponentTestTool.java:180)
at
org.apache.maven.shared.test.plugin.ComponentTestTool.prepareComponentForUnitTestingWithMavenBuilds(ComponentTestTool.java:121)
at
org.apache.maven.plugin.componentit.StagingBuildMojo.execute(StagingBuildMojo.java:90)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:650)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:419)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:293)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:150)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:219)
at
org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:819)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:418)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:85)
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.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:408)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:351)
This is a backward compatibility issue, and should be addressed in order to
ensure smooth migrations from 2.0.x to 2.1-alpha-1
was:
When I tried to run a the component-it-plugin from maven sandbox during an
integration-test run on the assembly plugin with a Maven build from Sept. 10,
2007, I got the following:
{noformat}
Exception in thread "main" java.lang.NoSuchMethodError:
org.apache.maven.settings.MavenSettingsBuilder.buildSettings()Lorg/apache/maven/settings/Settings;
at
org.apache.maven.shared.test.plugin.RepositoryTool.findLocalRepositoryDirectory(RepositoryTool.java:100)
at
org.apache.maven.shared.test.plugin.ProjectTool.manglePomForTesting(ProjectTool.java:301)
at
org.apache.maven.shared.test.plugin.ProjectTool.packageProjectArtifact(ProjectTool.java:168)
at
org.apache.maven.shared.test.plugin.ComponentTestTool.prepareForTesting(ComponentTestTool.java:180)
at
org.apache.maven.shared.test.plugin.ComponentTestTool.prepareComponentForUnitTestingWithMavenBuilds(ComponentTestTool.java:121)
at
org.apache.maven.plugin.componentit.StagingBuildMojo.execute(StagingBuildMojo.java:90)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:650)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:419)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:293)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:150)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:219)
at
org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:819)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:418)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:85)
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.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at
org.codehaus.plexus.classworld
[jira] Updated: (MNG-3206) Changes to MavenSettingsBuilder breaks backward compatibility
[ http://jira.codehaus.org/browse/MNG-3206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Casey updated MNG-3206: Fix Version/s: 2.1-alpha-1 > Changes to MavenSettingsBuilder breaks backward compatibility > - > > Key: MNG-3206 > URL: http://jira.codehaus.org/browse/MNG-3206 > Project: Maven 2 > Issue Type: Bug > Components: Settings >Affects Versions: 2.1-alpha-1 >Reporter: John Casey >Priority: Blocker > Fix For: 2.1-alpha-1 > > > When I tried to run a the component-it-plugin from maven sandbox during an > integration-test run on the assembly plugin with a Maven build from Sept. 10, > 2007, I got the following: > Exception in thread "main" java.lang.NoSuchMethodError: > org.apache.maven.settings.MavenSettingsBuilder.buildSettings()Lorg/apache/maven/settings/Settings; > at > org.apache.maven.shared.test.plugin.RepositoryTool.findLocalRepositoryDirectory(RepositoryTool.java:100) > at > org.apache.maven.shared.test.plugin.ProjectTool.manglePomForTesting(ProjectTool.java:301) > at > org.apache.maven.shared.test.plugin.ProjectTool.packageProjectArtifact(ProjectTool.java:168) > at > org.apache.maven.shared.test.plugin.ComponentTestTool.prepareForTesting(ComponentTestTool.java:180) > at > org.apache.maven.shared.test.plugin.ComponentTestTool.prepareComponentForUnitTestingWithMavenBuilds(ComponentTestTool.java:121) > at > org.apache.maven.plugin.componentit.StagingBuildMojo.execute(StagingBuildMojo.java:90) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:650) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:419) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:293) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:150) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:219) > at > org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:819) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:418) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:85) > 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.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) > at > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:408) > at > org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:351) > This is a backward compatibility issue, and should be addressed in order to > ensure smooth migrations from 2.0.x to 2.1-alpha-1 -- 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-3206) Changes to MavenSettingsBuilder breaks backward compatibility
Changes to MavenSettingsBuilder breaks backward compatibility
-
Key: MNG-3206
URL: http://jira.codehaus.org/browse/MNG-3206
Project: Maven 2
Issue Type: Bug
Components: Settings
Affects Versions: 2.1-alpha-1
Reporter: John Casey
Priority: Blocker
Fix For: 2.1-alpha-1
When I tried to run a the component-it-plugin from maven sandbox during an
integration-test run on the assembly plugin with a Maven build from Sept. 10,
2007, I got the following:
{noformat}
Exception in thread "main" java.lang.NoSuchMethodError:
org.apache.maven.settings.MavenSettingsBuilder.buildSettings()Lorg/apache/maven/settings/Settings;
at
org.apache.maven.shared.test.plugin.RepositoryTool.findLocalRepositoryDirectory(RepositoryTool.java:100)
at
org.apache.maven.shared.test.plugin.ProjectTool.manglePomForTesting(ProjectTool.java:301)
at
org.apache.maven.shared.test.plugin.ProjectTool.packageProjectArtifact(ProjectTool.java:168)
at
org.apache.maven.shared.test.plugin.ComponentTestTool.prepareForTesting(ComponentTestTool.java:180)
at
org.apache.maven.shared.test.plugin.ComponentTestTool.prepareComponentForUnitTestingWithMavenBuilds(ComponentTestTool.java:121)
at
org.apache.maven.plugin.componentit.StagingBuildMojo.execute(StagingBuildMojo.java:90)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:650)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:419)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:293)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:150)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:219)
at
org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:819)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:418)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:85)
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.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:408)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:351)
{noformat}
This is a backward compatibility issue, and should be addressed in order to
ensure smooth migrations from 2.0.x to 2.1-alpha-1
--
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-2133) plugin goal skipped if not bound to any phase and no default phase exists in the mojo.
[ http://jira.codehaus.org/browse/MNG-2133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107169 ] werner mueller commented on MNG-2133: - is this one related to the issue http://jira.codehaus.org/browse/MSOURCES-19 ? (i did submit it there by mistake) > plugin goal skipped if not bound to any phase and no default phase exists in > the mojo. > -- > > Key: MNG-2133 > URL: http://jira.codehaus.org/browse/MNG-2133 > Project: Maven 2 > Issue Type: Bug > Components: Plugins and Lifecycle >Reporter: Prasad Kashyap > Fix For: 2.1 > > > In a pom, if no phase is specified for a plugin, then it is bound to the > default phase defined by the mojo. > However, if the mojo doesn't have a default phase, then it currently seems to > be skipped, which is a probably incorrect. -- 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: (MWAR-116) The outputFileNameMapping config creates bad dependency files in WEB-INF/lib
[
http://jira.codehaus.org/browse/MWAR-116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107165
]
Chris Moesel commented on MWAR-116:
---
I failed to mention this in the description, but I only tested using Maven
2.0.4. I do not have Maven 2.1-beta-1 on my system. So in this case, the war
plugin was the only component from 2.1-beta-1.
> The outputFileNameMapping config creates bad dependency files in WEB-INF/lib
>
>
> Key: MWAR-116
> URL: http://jira.codehaus.org/browse/MWAR-116
> Project: Maven 2.x War Plugin
> Issue Type: Bug
>Affects Versions: 2.1-alpha-1
>Reporter: Chris Moesel
>Assignee: Stephane Nicoll
> Attachments: mwar_93_webapp.zip
>
>
> I've tried using the new outputFileNameMapping feature (MWAR-93) by adding
> the following to my POM:
>
> org.apache.maven.plugins
> maven-war-plugin
> 2.1-alpha-1-SNAPSHOT
>
> ${artifactId}.${extension}
>
>
> This results in really oddly named files in my web-inf/lib now. A typical
> example:
> org.springframework-mywebapp.null
> So, the resulting files are really mapped more like: ${groupId of the
> dependency}-${artifactId of my war module}.null
> I've attached an example Maven 2 project that demonstrates this. Just run
> "mvn package" and look at the result in 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: (MRM-496) adding a proxy connector action is not working after repository changes
adding a proxy connector action is not working after repository changes --- Key: MRM-496 URL: http://jira.codehaus.org/browse/MRM-496 Project: Archiva Issue Type: Bug Components: web application Affects Versions: 1.0-beta-2 Reporter: Brett Porter Fix For: 1.0-beta-2 need to write tests also, and run through the related issues for proxy connector admin in JIRA -- 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-496) adding a proxy connector action is not working after repository changes
[ http://jira.codehaus.org/browse/MRM-496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MRM-496: - Fix Version/s: 1.0-beta-2 > adding a proxy connector action is not working after repository changes > --- > > Key: MRM-496 > URL: http://jira.codehaus.org/browse/MRM-496 > Project: Archiva > Issue Type: Bug > Components: web application >Affects Versions: 1.0-beta-2 >Reporter: Brett Porter >Assignee: Brett Porter > Fix For: 1.0-beta-2 > > > need to write tests also, and run through the related issues for proxy > connector admin in JIRA -- 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: (MRM-495) search fields should be weighted to improve search results
search fields should be weighted to improve search results -- Key: MRM-495 URL: http://jira.codehaus.org/browse/MRM-495 Project: Archiva Issue Type: Improvement Components: indexing Reporter: Brett Porter -- 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: (MRM-494) leaving repository ID blank on the add repository page goes to the edit page where ID cannot be edited
leaving repository ID blank on the add repository page goes to the edit page where ID cannot be edited -- Key: MRM-494 URL: http://jira.codehaus.org/browse/MRM-494 Project: Archiva Issue Type: Bug Components: web application Reporter: Brett Porter -- 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: (SCM-342) scm:tag should support flat project layout
[
http://jira.codehaus.org/browse/SCM-342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107162
]
Emmanuel Venisse commented on SCM-342:
--
Normally, all SCM tools tag recursively but it won't work in some case.
With subversion (it can be the same for cvs and others), some users use a flat
layout on their own machine but not in the SCM. for exemple with svn:
in svn:
{noformat}
ROOT/
module1/
branches/
tags/
trunk/
pom.xml
module2/
branches/
tags/
trunk/
pom.xml
{noformat}
and in working copy:
{noformat}
ROOT/
module1/
pom.xml
module2/
pom.xml
{noformat}
With this structure, some users will want a global tag under ROOT/tags/ and
some others will want one tag by module under /ROOT/moduleX/tags/
> scm:tag should support flat project layout
> --
>
> Key: SCM-342
> URL: http://jira.codehaus.org/browse/SCM-342
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-plugin
>Affects Versions: 1.0
> Environment: Windows XP, Eclipse 3.3
>Reporter: Duncan Doyle
>
> I have a Maven2 Flat Project Layout as described here:
> http://maven.apache.org/guides/mini/guide-ide-eclipse.html
> Basically my directory layout is as follows:
> /MavenRoot/pom.xml (this is the SuperPom)
> /Module1/pom.xml
> /Module2/pom.xml
> /Module3/pom.xml
> Modules 1,2 and 3 are specified in the section of the SuperPom
> (e.g() ../Module1). Each POM contains its own CVS connection
> URL.
> When I execute the scm:tag goal on the SuperPom in the MavenRoot project,
> only the MavenRoot project gets tagged. The same behaviour can be seen with
> the scm:update goal, which was fixed by providing a scm:update-subprojects
> goal.
> I would like to see this behaviour fixed in the SCM plugin, while Maven2
> advices a Flat Project Layout when working with Eclipse. At this moment I
> can't use the tag goal at all (it should be executed automatically by
> CruiseControl on a succesfull build).
--
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: (MRM-493) Downloaded artifacts are stored in incorrect archiva-managed repository
Downloaded artifacts are stored in incorrect archiva-managed repository
---
Key: MRM-493
URL: http://jira.codehaus.org/browse/MRM-493
Project: Archiva
Issue Type: Bug
Components: remote proxy
Affects Versions: 1.0-beta-2
Environment: Linux 2.6.20-16-server i686 GNU/Linux,
Sun Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_11-b03),
apache-archiva-1.0-beta-2-SNAPSHOT (2007-09-11)
Reporter: Jo Vandermeeren
I have added a new local directory as archiva-managed repository with id
"repo-trax".
Although no proxy connector has been setup for this new archiva-managed
repository, downloaded artifacts seem to be stored in this repository instead
of the default "internal" repository.
The only proxy connector configuration is the one that comes by default
("internal" connected to dev.java.net and repo1.maven.org).
--
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: (MWAR-117) Decompose package between prepare-package and package
[ http://jira.codehaus.org/browse/MWAR-117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107157 ] Stephane Nicoll commented on MWAR-117: -- This is not linked to the plugin. This has already been addressed ten times on the list and it's more related to the available phases. the plugins you want to add, you will bind them to a phase right? Which one? > Decompose package between prepare-package and package > - > > Key: MWAR-117 > URL: http://jira.codehaus.org/browse/MWAR-117 > Project: Maven 2.x War Plugin > Issue Type: Wish >Affects Versions: 2.1-alpha-1 >Reporter: Hervé Rolland >Priority: Minor > > In prepare-package : prepare working directory, resolve dependency and overlay > In package : build war > In that way we can add plugin in prepare-package phase for update webapp > source files -- 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: (MSANDBOX-36) [jxr] tools/forrestdoc needs general tidy up and some documentation to encourage its use
[jxr] tools/forrestdoc needs general tidy up and some documentation to encourage its use Key: MSANDBOX-36 URL: http://jira.codehaus.org/browse/MSANDBOX-36 Project: Maven 2.x Sandbox Issue Type: Improvement Components: jxr Reporter: Vincent Siveton tools/forrestdoc needs general tidy up and some documentation to encourage its use. See collection of some links in http://marc.theaimsgroup.com/?l=forrest-dev&m=114082527806288 Refer to https://issues.apache.org/jira/browse/FOR-820 -- 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: (CONTINUUM-1395) check the permissions on the add project action for ant projects
[ http://jira.codehaus.org/browse/CONTINUUM-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse closed CONTINUUM-1395. --- Resolution: Fixed Fixed in r.574916 > check the permissions on the add project action for ant projects > > > Key: CONTINUUM-1395 > URL: http://jira.codehaus.org/browse/CONTINUUM-1395 > Project: Continuum > Issue Type: Bug > Components: Integration - Ant >Affects Versions: 1.1-beta-2 >Reporter: Brett Porter >Assignee: Emmanuel Venisse > Fix For: 1.1-beta-3 > > > On vmbuild1, I found that one person with the correct permissions assigned > for a project (as an administrator) failed to add an Ant project. They were > given the option, and could enter the details into the form, but it failed > with a permission error after that. > It succeeded for me, though I have all privileges other than System > Administrator. > The project was being added to an existing group, via the button on the group > page. > There are two possible causes: > - certain project types check the wrong permission. I find this the most > likely - it's probably tied to the other user not being able to see the "add > project" buttons in the left navigation as they only have that permission > within certain groups. They are able to perform other operations on the group. > - the roles did not associate properly (though I tried recreating the group, > and the user tried logging out/in again). > I'd like to confirm whether the first can be reproduced before checking the > database for the second. -- 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: (MSANDBOX-35) [jxr] JavaSrcTask needs to handle a custom bottom
[jxr] JavaSrcTask needs to handle a custom bottom
-
Key: MSANDBOX-35
URL: http://jira.codehaus.org/browse/MSANDBOX-35
Project: Maven 2.x Sandbox
Issue Type: Improvement
Components: jxr
Reporter: Vincent Siveton
We need to handle a custom bottom instead to have static one: the following
code is harcoded in Pass2.java
{noformat}
Copyright © 2001-2003 Apache Software Foundation. All Rights Reserved.
{noformat}
Refer to https://issues.apache.org/jira/browse/FOR-1030
--
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: (MSANDBOX-34) [jxr] Error for dot target in java.xml
[jxr] Error for dot target in java.xml
--
Key: MSANDBOX-34
URL: http://jira.codehaus.org/browse/MSANDBOX-34
Project: Maven 2.x Sandbox
Issue Type: Bug
Components: jxr
Reporter: Vincent Siveton
Using the rev 554901 of forrestdoc, the dot target in the src/java.xml produces
errors on Windows with graphviz-2.12.
Here is an extract of the build output:
{noformat}
xml2dot:
Processing
D:\temp\forrest\whiteboard\forrestdoc\build\forrestdoc\forrestdoc\xml\xmldocs.xml
to
D:\temp\forrest\whiteboard\forrestdoc\build\forrestdoc\forrestdoc\dot\graph.dot
Loading stylesheet
D:\temp\forrest\whiteboard\forrestdoc\src\resources\javadoc\xml2dot.xsl
dot:
Error:
D:\temp\forrest\whiteboard\forrestdoc\build\forrestdoc\forrestdoc\dot/graph.dot:3:
syntax error near line 3
context: >>> Converts <<< path and classpath information to a specific target OS
Warning:
D:\temp\forrest\whiteboard\forrestdoc\build\forrestdoc\forrestdoc\dot/graph.dot:190:
string ran past end of line
Warning:
D:\temp\forrest\whiteboard\forrestdoc\build\forrestdoc\forrestdoc\dot/graph.dot:249:
string ran past end of line
Result: 1
uml:
Using Project dir: D:\temp\forrest\whiteboard\forrestdoc
Using Target dir: D:\temp\forrest\whiteboard\forrestdoc\build\forrestdoc\for
restdoc
ant buildfine available: true
dot:
Error:
D:\temp\forrest\whiteboard\forrestdoc\build\forrestdoc\forrestdoc\dot/graph.dot:3:
syntax error near line 3
context: >>> Converts <<< path and classpath information to a specific target OS
Warning:
D:\temp\forrest\whiteboard\forrestdoc\build\forrestdoc\forrestdoc\dot/graph.dot:190:
string ran past end of line
Warning:
D:\temp\forrest\whiteboard\forrestdoc\build\forrestdoc\forrestdoc\dot/graph.dot:249:
string ran past end of line
Result: 1
{noformat}
It seems that the xml2dot target produces wrong graph.dot.
Here is an extract from build\forrestdoc\forrestdoc\dot\graph.dot
{noformat}
Converts path and classpath information to a specific target OS
format. The resulting formatted path is placed into the specified property.Ant
1.4
category="utility"
constructor
Create a nested PATH element
...
{noformat}
Refer to https://issues.apache.org/jira/browse/FOR-1023
--
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: (MSANDBOX-33) [jxr] Split forrestdoc source to provide more artifacts
[jxr] Split forrestdoc source to provide more artifacts --- Key: MSANDBOX-33 URL: http://jira.codehaus.org/browse/MSANDBOX-33 Project: Maven 2.x Sandbox Issue Type: Task Components: jxr Reporter: Vincent Siveton Not sure about this one in the Forrest way, but it seems to be a good idea to split the forrestdoc source to provide 3 artifacts: * one for javasrc * one for ant * one for js Based on http://issues.apache.org/jira/browse/FOR-1028 -- 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-457) don't display the snapshot removal options in the repository list page if snapshots are not included
[ http://jira.codehaus.org/browse/MRM-457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed MRM-457. Resolution: Fixed > don't display the snapshot removal options in the repository list page if > snapshots are not included > > > Key: MRM-457 > URL: http://jira.codehaus.org/browse/MRM-457 > Project: Archiva > Issue Type: Improvement >Affects Versions: 1.0-beta-1 >Reporter: Brett Porter >Assignee: Brett Porter > Fix For: 1.0-beta-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] Closed: (MRM-441) removing a "remote repository" should not present the page about handling content
[ http://jira.codehaus.org/browse/MRM-441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed MRM-441. Resolution: Fixed > removing a "remote repository" should not present the page about handling > content > - > > Key: MRM-441 > URL: http://jira.codehaus.org/browse/MRM-441 > Project: Archiva > Issue Type: Bug >Affects Versions: 1.0-alpha-2 >Reporter: Brett Porter >Assignee: Brett Porter > Fix For: 1.0-beta-2 > > > eg. delete the default java.net repository when starting a new installation. > Expected result: a confirmation page (yes/no only) about whether to remove it > Actual result: the normal managed repository page about deleting the > repository definition, contents, or going back -- 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-144) fix miscellaneous tasks listed in important TODO items
[ http://jira.codehaus.org/browse/MRM-144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed MRM-144. Resolution: Fixed > fix miscellaneous tasks listed in important TODO items > -- > > Key: MRM-144 > URL: http://jira.codehaus.org/browse/MRM-144 > Project: Archiva > Issue Type: Task > Components: design >Reporter: Brett Porter >Assignee: Brett Porter > Fix For: 1.0-beta-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] Created: (MRM-492) repository failures can present as a 404 from proxy
repository failures can present as a 404 from proxy --- Key: MRM-492 URL: http://jira.codehaus.org/browse/MRM-492 Project: Archiva Issue Type: Improvement Components: remote proxy Reporter: Brett Porter if multiple repositories are a proxy source and it is not found on some, and an error occurs on one or more - the end result is a "not found", where there should be some indication of error in case the artifact may exist on the repository with the error. -- 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: (MRM-491) paginate report pages
paginate report pages - Key: MRM-491 URL: http://jira.codehaus.org/browse/MRM-491 Project: Archiva Issue Type: Improvement Components: web application Reporter: Brett Porter - artifact dependencies - artifact used by -- 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: (MRM-490) add xwork exception handling pages for presentable error reporting
add xwork exception handling pages for presentable error reporting -- Key: MRM-490 URL: http://jira.codehaus.org/browse/MRM-490 Project: Archiva Issue Type: Bug Components: web application Reporter: Brett Porter if anyone gets a stack trace, they should have an easy way to report it as a bug (though this should also be configurable since in a production environment the admin would want to be contacted instead) -- 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-462) separate configuration of managed repositories from remote repositories
[ http://jira.codehaus.org/browse/MRM-462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed MRM-462. Resolution: Fixed merged > separate configuration of managed repositories from remote repositories > --- > > Key: MRM-462 > URL: http://jira.codehaus.org/browse/MRM-462 > Project: Archiva > Issue Type: Bug > Components: web application >Affects Versions: 1.0-beta-1 >Reporter: Brett Porter >Assignee: Brett Porter >Priority: Critical > Fix For: 1.0-beta-2 > > > the fancy footwork to make a managed repository use all the same > configuration screens as a remote repository is causing both subtle bugs > (particularly in the URL handling), and a confusing user experience (settings > appearing that are irrelevant to remote repositories in the edit form). > 1) separate the forms/actions (or at least exclude the fields that are not > relevant when editing the remote repos) > 2) treat the URL (remote) as a URL and the location (managed) as a path. > Don't munge anything. > 3) I think we should consider separating them into different lists in the > configuration again. -- 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: (SCM-342) scm:tag should support flat project layout
[ http://jira.codehaus.org/browse/SCM-342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107132 ] Duncan Doyle commented on SCM-342: -- I'm currently developing a fix for this issue, however I need some more info about other SCM tools. I'm familiar with how CVS tagging works, but I need to know whether other SCM tools (SubVersion, ClearCase, etc.) have the same behaviour in order for my algorithm to work. So my question is if all SCM tools tag recursively (e.g. like CVS, tag the basedir all files in the directory tree which are under CVS control get tagged)? The algorithm I have in mind works like this. - Keep a static HashSet in the class which contains processed (tagged) base directories of the ScmFileSets. - When a project executes a tag, check whether the basedir of its ScmFileSet is in the set of already processed basedirs. If it is present in the list, don't execute the tagging for this project. Otherwise continue. - Check whether the basedir of the project's ScmFileSet is a subdirectory of an already processed basedir in the static HashSet. If it is a subdirectory, skip the tagging because it has already been tagged recursively by another project. Otherwise, continue. - Execute the tagging on the project and add the ScmFileSet's basedir to the static HashSet. Using this algorithm, the aggregator tag can be removed. If all SCM tools work like this, this algorithm will ensure correct tagging behaviour for boh standard - and flat project layouts. > scm:tag should support flat project layout > -- > > Key: SCM-342 > URL: http://jira.codehaus.org/browse/SCM-342 > Project: Maven SCM > Issue Type: Bug > Components: maven-plugin >Affects Versions: 1.0 > Environment: Windows XP, Eclipse 3.3 >Reporter: Duncan Doyle > > I have a Maven2 Flat Project Layout as described here: > http://maven.apache.org/guides/mini/guide-ide-eclipse.html > Basically my directory layout is as follows: > /MavenRoot/pom.xml (this is the SuperPom) > /Module1/pom.xml > /Module2/pom.xml > /Module3/pom.xml > Modules 1,2 and 3 are specified in the section of the SuperPom > (e.g() ../Module1). Each POM contains its own CVS connection > URL. > When I execute the scm:tag goal on the SuperPom in the MavenRoot project, > only the MavenRoot project gets tagged. The same behaviour can be seen with > the scm:update goal, which was fixed by providing a scm:update-subprojects > goal. > I would like to see this behaviour fixed in the SCM plugin, while Maven2 > advices a Flat Project Layout when working with Eclipse. At this moment I > can't use the tag goal at all (it should be executed automatically by > CruiseControl on a succesfull build). -- 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-3205) Switch to use maven-artifact 3.x
[ http://jira.codehaus.org/browse/MNG-3205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107129 ] Mark Hobson commented on MNG-3205: -- Active branches: https://svn.apache.org/repos/asf/maven/components/branches/MNG-3205/ https://svn.apache.org/repos/asf/maven/plugins/branches/maven-plugin-plugin-MNG-3205/ https://svn.apache.org/repos/asf/maven/core-integration-testing/branches/MNG-3205/ > Switch to use maven-artifact 3.x > > > Key: MNG-3205 > URL: http://jira.codehaus.org/browse/MNG-3205 > Project: Maven 2 > Issue Type: Improvement > Components: Artifacts and Repositories >Affects Versions: 2.0.7 >Reporter: Mark Hobson > > Remove maven-artifact 2.0.x, maven-artifact-manager 2.0.x and > maven-repository-metadata 2.0.x in preference of using maven-artifact 3.x. -- 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-3205) Switch to use maven-artifact 3.x
Switch to use maven-artifact 3.x Key: MNG-3205 URL: http://jira.codehaus.org/browse/MNG-3205 Project: Maven 2 Issue Type: Improvement Components: Artifacts and Repositories Affects Versions: 2.0.7 Reporter: Mark Hobson Remove maven-artifact 2.0.x, maven-artifact-manager 2.0.x and maven-repository-metadata 2.0.x in preference of using maven-artifact 3.x. -- 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: (CONTINUUM-1444) IRC and Jabber notifiers accept invalid ports.
[ http://jira.codehaus.org/browse/CONTINUUM-1444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse closed CONTINUUM-1444. --- Assignee: Emmanuel Venisse Resolution: Fixed Fix Version/s: 1.1-beta-3 Applied. Thanks > IRC and Jabber notifiers accept invalid ports. > -- > > Key: CONTINUUM-1444 > URL: http://jira.codehaus.org/browse/CONTINUUM-1444 > Project: Continuum > Issue Type: Improvement > Components: Web - UI >Reporter: Teodoro Cue Jr. >Assignee: Emmanuel Venisse >Priority: Minor > Fix For: 1.1-beta-3 > > Attachments: CONTINUUM-1444-continuum-webapp.patch > > > Port range is from 0 to 65535. Beyond this, the user should be given an error. -- 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: (MAVENUPLOAD-1713) Upload grails-maven-plugin 0.1
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arnaud Heritier updated MAVENUPLOAD-1713: - Attachment: grails-0.5.6-launch-0.1-bundle.jar The last one > Upload grails-maven-plugin 0.1 > -- > > Key: MAVENUPLOAD-1713 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1713 > Project: maven-upload-requests > Issue Type: Task >Reporter: Arnaud Heritier > Attachments: grails-0.5.6-base-0.1-bundle.jar, > grails-0.5.6-launch-0.1-bundle.jar, grails-0.5.6-poms-0.1-bundle.jar, > grails-0.5.6-web-0.1-bundle.jar > > > The parent pom is also needed : > http://forge.octo.com/downloads/mtg-0.1-bundle.jar > The Grails plugin for maven is a set of goals to easily develop a Grails > application using maven 2. > 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] Updated: (MAVENUPLOAD-1713) Upload grails-maven-plugin 0.1
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arnaud Heritier updated MAVENUPLOAD-1713: - Attachment: grails-0.5.6-web-0.1-bundle.jar grails-0.5.6-base-0.1-bundle.jar grails-0.5.6-poms-0.1-bundle.jar Some poms also required by our users > Upload grails-maven-plugin 0.1 > -- > > Key: MAVENUPLOAD-1713 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1713 > Project: maven-upload-requests > Issue Type: Task >Reporter: Arnaud Heritier > Attachments: grails-0.5.6-base-0.1-bundle.jar, > grails-0.5.6-poms-0.1-bundle.jar, grails-0.5.6-web-0.1-bundle.jar > > > The parent pom is also needed : > http://forge.octo.com/downloads/mtg-0.1-bundle.jar > The Grails plugin for maven is a set of goals to easily develop a Grails > application using maven 2. > 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] Updated: (CONTINUUM-1445) Impossible to add two projects with the same name even if they have differents version and/or scmUrl
[ http://jira.codehaus.org/browse/CONTINUUM-1445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated CONTINUUM-1445: Fix Version/s: 1.1-beta-3 Summary: Impossible to add two projects with the same name even if they have differents version and/or scmUrl (was: Impossible to add two projects with the same name even if they are in different groups) > Impossible to add two projects with the same name even if they have > differents version and/or scmUrl > > > Key: CONTINUUM-1445 > URL: http://jira.codehaus.org/browse/CONTINUUM-1445 > Project: Continuum > Issue Type: Bug > Components: Core system, Web - UI >Affects Versions: 1.1-beta-2 >Reporter: Olivier Lamy >Assignee: Olivier Lamy > Fix For: 1.1-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: (MNG-3204) Parallel dependency fetching
Parallel dependency fetching Key: MNG-3204 URL: http://jira.codehaus.org/browse/MNG-3204 Project: Maven 2 Issue Type: Improvement Components: Performance Affects Versions: 2.0.7 Reporter: Marat Radchenko On projects with many dependencies initial dependency fetch process can be very slow (20 minutes+). It could be greately speeded up by using parallel fetching. -- 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: (CONTINUUM-1445) Impossible to add two projects with the same name even if they are in different groups
[ http://jira.codehaus.org/browse/CONTINUUM-1445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107118 ] Olivier Lamy commented on CONTINUUM-1445: - The test to prevent duplicate projects must be changed to add test on projectname and version and scmurl. But must be on all projects because a project can be moved to another group. > Impossible to add two projects with the same name even if they are in > different groups > -- > > Key: CONTINUUM-1445 > URL: http://jira.codehaus.org/browse/CONTINUUM-1445 > Project: Continuum > Issue Type: Bug > Components: Core system, Web - UI >Affects Versions: 1.1-beta-2 >Reporter: Olivier Lamy >Assignee: Olivier Lamy > -- 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: (CONTINUUM-1445) Impossible to add two projects with the same name even if they are in different groups
Impossible to add two projects with the same name even if they are in different groups -- Key: CONTINUUM-1445 URL: http://jira.codehaus.org/browse/CONTINUUM-1445 Project: Continuum Issue Type: Bug Components: Core system, Web - UI Affects Versions: 1.1-beta-2 Reporter: Olivier Lamy -- 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
