It was... I cloned them first :)
On 02/04/2008, at 8:16 PM, Emmanuel Venisse wrote:
Why a move and not a copy? same question for MRM-760
Emmanuel
On Wed, Apr 2, 2008 at 5:44 AM, Brett Porter (JIRA)
<[EMAIL PROTECTED]>
wrote:
[
http://jira.codehaus.org/browse/MRM-75
Why a move and not a copy? same question for MRM-760
Emmanuel
On Wed, Apr 2, 2008 at 5:44 AM, Brett Porter (JIRA) <[EMAIL PROTECTED]>
wrote:
>
> [
> http://jira.codehaus.org/browse/MRM-759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel]
>
> Brett P
I just updated http://jira.codehaus.org/browse/MRM-594 to attach a new
patch. This one fully solves the issue by providing storage of the
configuration in archvia XML configuration and a management Web UI.
Nico.
ed a customized archiva instance to replace my
> > corporate
> > repository. It uses archiva SVN + the patches I provided for
> > MRM-594 595
> > &596.
> >
> > All works fine for both m1 and m2 builds on our projects.
> >
> > On MRM-594 : where cou
configuration sounds like the right place to me
On 16/11/2007, at 4:10 AM, nicolas de loof wrote:
Just FYI, I deployed a customized archiva instance to replace my
corporate
repository. It uses archiva SVN + the patches I provided for
MRM-594 595
&596.
All works fine for both m1 an
On 09/11/2007, at 5:48 AM, Joakim Erdfelt wrote:
1) Repository Configuration Create
2) Repository Configuration Edit
3) Repository Configuration Delete
4) Proxy Connector Create
5) Proxy Connector Edit
6) Proxy Connector Delete
I would put these in a separate log, probably
7) Metadata Merge
I'm not so sure, but I'm happy to push it out - have done so.
- Brett
On 09/11/2007, at 2:41 AM, Joakim Erdfelt wrote:
I'm working through the open jiras and i keep coming across this one.
[MRM-435] Need to review repository defaults
Description: we should review the use o
A change was made to audit logging today (re: MRM-564)
The audit.log is now generated via a log4j logger (not direct java.io
usage).
The output contains the following structure.
"{timestamp} {repository_id} {user_id} {remote_ip} \"{resource}\"
\"{action}\""
I'm working through the open jiras and i keep coming across this one.
[MRM-435] Need to review repository defaults
Description: 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 be
Brett Porter wrote:
On 01/11/2007, at 10:01 AM, Joakim Erdfelt wrote:
IGNORED is a universal setting that means ... "This policy is ignored."
It can be applied to any policy.
Changing IGNORED to ALWAYS is makes no sense for the other policies.
I wasn't suggesting this for anything but releas
wrote:
There seems to be some confusion on the settings, defaults values,
meanings, purpose, etc...
http://jira.codehaus.org/browse/MRM-549
* MRM-549 : proxy connectors: no "always" option for releases and
snapshots policies
http://jira.codehaus.org/browse/MRM-547
* MRM-547 : prox
This has been sitting out there a while now with the major changes in
place, and I've finished up the webapp today and added tests. I'll
start merging it onto trunk!
- Brett
On 18/08/2007, at 11:46 PM, Brett Porter wrote:
I decided to use a branch for the configuration split since I
thoug
Brett Porter wrote:
This seems to make sense (though the concurrency issues are
concerning, especially considering difficulty to test)
- Brett
On 31/08/2007, at 2:56 AM, Joakim Erdfelt wrote:
In the past 2 weeks I've made tremendous progress on the Metadata
issues within Archiva.
So far in
n.
Arnaud
On 21/08/07, Brett Porter <[EMAIL PROTECTED]> wrote:
I'm not merging until I'm done, and I'll give a heads up.
But please, be nice... :)
Actually, maybe we should race. Loser has to resolve the
conflicts! :)
- Brett
On 21/08/2007, at 1:04 PM, Joakim Erdfelt wrot
. :)
>
> Actually, maybe we should race. Loser has to resolve the conflicts! :)
>
> - Brett
>
> On 21/08/2007, at 1:04 PM, Joakim Erdfelt wrote:
>
> > I have a decent raft of new code coming in as part of MRM-463
> > (metadata stuff), can you hold off until that co
Wendy Smoak wrote:
On 7/25/07, Maria Odea Ching <[EMAIL PROTECTED]> wrote:
I'm trying to fix up MRM-294, and I need your input/comments :-)
Should the configuration for the repository purge be for each
repository? If so, I think it can be consolidated with the repository
scanning s
Yep, I'm also saying (b) :)
Thanks,
Deng
Brett Porter wrote:
On 25/07/2007, at 9:09 PM, Maria Odea Ching wrote:
Sorry, I think I confused you more. Anyway, that's what I meant by #3
:-) So if I specified "5", then it would keep 5 in total of the
latest if the snapshot's count in the repo is
]> wrote:
Arnaud Heritier<
http://jira.codehaus.org/secure/ViewProfile.jspa?name=aheritier>commented
on 11 march about commiting the patch for issue MRM-212 (checksum
policy)
Is there any work in progress about it ?
Nico.
Arnaud
Heritier<http://jira.codehaus.org/secure/ViewProfile.jspa?name=aheritier>commented
on 11 march about commiting the patch for issue MRM-212 (checksum
policy)
Is there any work in progress about it ?
Nico.
wrote:
+1
Emmanuel
Joakim Erdfelt a écrit :
> I would like to merge the archiva-MRM-239 branch back to trunk.
>
> Not sure how long I should wait for the vote replies, but I'll
do the
> usual 72.
>
> - Joakim
>
>
>
>
>>> One thing before ...
>>> Can we have the list of patchs that aren't yet applied on the trunk ?
>>> Don't we have to apply them before or we'll never be able to do it
>>> (due to
>>> the important changes you made) ?
>>>
>>
e able to do it
(due to
the important changes you made) ?
Arnaud
On 2/23/07, Emmanuel Venisse <[EMAIL PROTECTED]> wrote:
+1
Emmanuel
Joakim Erdfelt a écrit :
> I would like to merge the archiva-MRM-239 branch back to trunk.
>
> Not sure how long I should wait for the vote replies, but I'll
do the
> usual 72.
>
> - Joakim
>
>
>
uel
Joakim Erdfelt a écrit :
> I would like to merge the archiva-MRM-239 branch back to trunk.
>
> Not sure how long I should wait for the vote replies, but I'll do the
> usual 72.
>
> - Joakim
>
>
>
+1
Emmanuel
Joakim Erdfelt a écrit :
I would like to merge the archiva-MRM-239 branch back to trunk.
Not sure how long I should wait for the vote replies, but I'll do the
usual 72.
- Joakim
PROTECTED]> wrote:
>
> I would like to merge the archiva-MRM-239 branch back to trunk.
>
> Not sure how long I should wait for the vote replies, but I'll do the
> usual 72.
>
> - Joakim
>
+1
Great work !!
Arnaud
On 2/22/07, Joakim Erdfelt <[EMAIL PROTECTED]> wrote:
I would like to merge the archiva-MRM-239 branch back to trunk.
Not sure how long I should wait for the vote replies, but I'll do the
usual 72.
- Joakim
On 2/17/07, Carlos Sanchez <[EMAIL PROTECTED]> wrote:
Somebody will correct me if i'm wrong ;) but the convention for
closing jira issues is to assign to yourself, and if there's no needed
work, like this case, it wouldn't be "fixed" (or it'll show up in the
changelog) but one of the others "won
fix", "incomplete" or "cannot
reproduce"
On 2/17/07, Wendy Smoak (JIRA) <[EMAIL PROTECTED]> wrote:
[
http://jira.codehaus.org/browse/MRM-283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wendy Smoak closed MRM-283.
I've attached a Path to return a "ProxiedArtifact" instead of a File from
ProxyRequestHandler
The test case has also be updated
The ProxiedDavServer can then update pathInfo and to return the expected
artifact.
Nico.
2007/2/14, Joakim Erdfelt <[EMAIL PROTECTED]>:
Or refactor the repository c
Or refactor the repository conversion routines a bit to expose the path
conversion routines. ;-)
Archiva is undergoing a lot of work right now.
Please keep us honest and get those jira's filed.
- Joakim
nicolas de loof wrote:
> I've reopened this issue as the DAV-based request (/repository/id)
>
I've reopened this issue as the DAV-based request (/repository/id) replacing
the proxy-based request (/proxy/id) has broken this feature.
As explained in Jira, the ProxiedDavServer doesn't use the result of the
proxyRequestHandler.get() method invocation, that may have changed the
target path. So
Hello,
On maven2 public repo, M1 plugins have a wrong ".plugin" extension.
This looks like a repo converter bug, and I've created MRM-224 for it.
This seems to be related to MRM-211 : there is no M1 plugin
ArtifactHandler in default Maven2 plexus configuration. But this also
Joakim,
looks really cool. I definitely think that it's would be valuable to
have as part of the indexed stuff in MRM. I will probably use it in
the Netbeans integration as well (either as part of MRM stuff or
separately for dependency management)
Unrelated, but I cannot resist:
When
-shared-jar to obtain the details of
the jar files.
I want to add this level of detail to the indexed information on MRM for
use
in the browse and search results screens. Hoping to show the user of
MRM that
the artifact they are considering is for JDK 1.5, has no debug
information, and
is using
Build your maven-jar-plugin from svn then try to build mrm again.
-allan
David Beckedorff wrote:
What is the fix for this? I'm using maven-2.0.4.
[INFO] Installing
D:\MRM\maven-repository-manager-site\maven-repository-application\target\m
aven-repository-applicatio
What is the fix for this? I'm using maven-2.0.4.
>>>
[INFO] Installing
D:\MRM\maven-repository-manager-site\maven-repository-application\target\m
aven-repository-application-1.0-SNAPSHOT.jar to C:\Documents and
Settings\dbeckedorff\.m2\re
pository\org\apache\maven\re
What is the current status & likely availability date for MRM? Is it
recommended to use Maven Proxy in the interim? If so, what repository names
should be set up for Proxy to allow for a amooth transition to MRM?
Thanks,
David
___
David Beckedorff
Se
dex in the repository.
- Brett
Felipe Leme wrote:
> Hi Brett, Jason and others,
>
> I'm trying to set up MRM at work and I'd like a little help, as there
> is no documentation about it yet.
>
> Right now, I was able to modify plexus.xml, generate and deploy the
> war
Hi Brett, Jason and others,
I'm trying to set up MRM at work and I'd like a little help, as there
is no documentation about it yet.
Right now, I was able to modify plexus.xml, generate and deploy the
war, and create some directories on /tmp/MRM (which is the path I've
chosen on p
Hi Brett,
I've just tried to build it, and got the same issue (out of the box :-(
BTW, is there a web page for the MRM yet?
[]s,
-- Felipe
On 3/31/06, Brett Porter <[EMAIL PROTECTED]> wrote:
>
> It requires 2.1-SNAPSHOT of the jar plugin fro the jar:sign goal. I've
>
It requires 2.1-SNAPSHOT of the jar plugin fro the jar:sign goal. I've
deployed a new snapshot - hopefully this willl make it build out of the box.
- Brett
Henri Yandell wrote:
> I'm getting test errors when I build MRM via 'mvn install'. I'm on OS
> X, JDK
I'm getting test errors when I build MRM via 'mvn install'. I'm on OS
X, JDK 1.4, Maven 2.0.3.
Summary:
[INFO] Building Maven Repository Manager Artifact Applet
[INFO]task-segment: [install]
[INFO]
--
dex.
>
> Here's the scenario.
>
> You have an anonymous ant.jar, and want to find out what it is.
> Using the traditional hashing technique, the entire file is hashed and a
> unique hash identification string is calculated.
>
> A problem occurs when the jar file being in
when the jar file being interrogated against the MRM index
has had its contents recompressed without any real change to the bytecode.
I propose adding another key to the lucene document for an Artifact called "Bytecode
Hash".
I've mocked up a simple demonstration of this hash techni
[ http://jira.codehaus.org/browse/MRM-99?page=all ]
Edwin Punzalan closed MRM-99:
-
Resolution: Fixed
Patch applied. Thanks.
> Use RepositoryIndexSearchLayer for searching in Packa
[ http://jira.codehaus.org/browse/MRM-32?page=all ]
Maria Odea Ching closed MRM-32:
---
Resolution: Fixed
Lucene index was already created. All sub-tasks of this issue are already
finished.
> Repository Indexing
> ---
>
>
[ http://jira.codehaus.org/browse/MRM-99?page=all ]
Maria Odea Ching updated MRM-99:
Attachment: MRM-99-maven-repository-webapp.patch
> Use RepositoryIndexSearchLayer for searching in Packa
[ http://jira.codehaus.org/browse/MRM-98?page=all ]
Edwin Punzalan closed MRM-98:
-
Resolution: Fixed
Patch applied. Thanks.
> Use the plexus configuration for index and repository p
Use RepositoryIndexSearchLayer for searching in Packages
Key: MRM-99
URL: http://jira.codehaus.org/browse/MRM-99
Project: Maven Repository Manager
Type: Bug
Components: web application
Versions: 1.0
Use the plexus configuration for index and repository path
--
Key: MRM-98
URL: http://jira.codehaus.org/browse/MRM-98
Project: Maven Repository Manager
Type: Improvement
Components: web application
[ http://jira.codehaus.org/browse/MRM-36?page=all ]
Edwin Punzalan closed MRM-36:
-
Resolution: Fixed
Patch applied. Thanks.
> integration with discovery and scheduling
> -
>
> Key: MRM-36
&g
[ http://jira.codehaus.org/browse/MRM-42?page=all ]
Edwin Punzalan closed MRM-42:
-
Resolution: Fixed
Patch applied. Thanks.
> discover repository metadata
>
>
> Key: MRM-42
> URL: http://ji
[ http://jira.codehaus.org/browse/MRM-36?page=all ]
Maria Odea Ching updated MRM-36:
Attachment: MRM-36-maven-repository-webapp.patch
> integration with discovery and scheduling
> -
>
>
[ http://jira.codehaus.org/browse/MRM-42?page=all ]
Maria Odea Ching updated MRM-42:
Attachment: MRM-42-maven-repository-discovery.patch
> discover repository metadata
>
>
> Key: MRM-42
>
[ http://jira.codehaus.org/browse/MRM-42?page=all ]
Maria Odea Ching reopened MRM-42:
-
There was a bug found when integrated with the scheduler and indexer.
> discover repository metadata
>
>
>
[ http://jira.codehaus.org/browse/MRM-81?page=all ]
Edwin Punzalan closed MRM-81:
-
Resolution: Fixed
Patch applied. Thanks.
> Search web user interface
> -
>
> Key: MRM-81
> URL: http://ji
[ http://jira.codehaus.org/browse/MRM-81?page=all ]
John Tolentino updated MRM-81:
--
Attachment: MRM-81-maven-repository-webapp.diff
> Search web user interface
> -
>
> Key: MRM-81
> URL: http://ji
[ http://jira.codehaus.org/browse/MRM-81?page=all ]
John Tolentino updated MRM-81:
--
Attachment: (was: MRM-81-maven-repository-webapp.diff)
> Search web user interface
> -
>
> Key: MRM-81
>
[ http://jira.codehaus.org/browse/MRM-81?page=all ]
John Tolentino updated MRM-81:
--
Attachment: MRM-81-maven-repository-webapp.diff
> Search web user interface
> -
>
> Key: MRM-81
> URL: http://ji
[ http://jira.codehaus.org/browse/MRM-81?page=all ]
John Tolentino updated MRM-81:
--
Attachment: MRM-81-maven-repository-indexer.diff
> Search web user interface
> -
>
> Key: MRM-81
> URL: http://ji
[ http://jira.codehaus.org/browse/MRM-91?page=all ]
Edwin Punzalan closed MRM-91:
-
Resolution: Fixed
> create a second index with a subset of information, and have it compres
[ http://jira.codehaus.org/browse/MRM-91?page=all ]
Edwin Punzalan updated MRM-91:
--
Assign To: Edwin Punzalan
Remaining Estimate: 8 hours
Original Estimate: 8 hours
According to jason, its an index with the same output as what eu has
[ http://jira.codehaus.org/browse/MRM-41?page=all ]
Edwin Punzalan closed MRM-41:
-
Resolution: Fixed
Committed the missing files. Sorry about that.
> discover standalone POMs
>
>
> Key: MRM-41
>
[ http://jira.codehaus.org/browse/MRM-41?page=all ]
John Tolentino reopened MRM-41:
---
Test data which was included in the patch was not applied to committed code.
This causes build failure on clean checkout. Please reapply patch.
> discover standal
[ http://jira.codehaus.org/browse/MRM-59?page=all ]
Edwin Punzalan closed MRM-59:
-
Resolution: Fixed
> Proxy should work transparently with either maven 1.x or 2.x repositor
[ http://jira.codehaus.org/browse/MRM-40?page=all ]
Brett Porter updated MRM-40:
Assign To: Brett Porter (was: John Tolentino)
> associate artifacts with their pom and checksums
>
>
>
[ http://jira.codehaus.org/browse/MRM-59?page=comments#action_59376 ]
Brett Porter commented on MRM-59:
-
Can you describe the solution you are thinking of? 12 hours sounds like it
might be more than I was anticipating.
All I figured for this was:
- the MRM
[ http://jira.codehaus.org/browse/MRM-59?page=all ]
Edwin Punzalan updated MRM-59:
--
Remaining Estimate: 12 hours
Original Estimate: 12 hours
> Proxy should work transparently with either maven 1.x or 2.x repositor
[ http://jira.codehaus.org/browse/MRM-95?page=all ]
Edwin Punzalan closed MRM-95:
-
Resolution: Fixed
> Allow cache timeout configurations for each proxied remote reposit
[ http://jira.codehaus.org/browse/MRM-41?page=all ]
Edwin Punzalan closed MRM-41:
-
Resolution: Fixed
Patch applied. Thanks.
> discover standalone POMs
>
>
> Key: MRM-41
> URL: http://jira.code
[ http://jira.codehaus.org/browse/MRM-41?page=all ]
John Tolentino updated MRM-41:
--
Attachment: MRM-41-maven-repository-discovery.diff
> discover standalone POMs
>
>
> Key: MRM-41
> URL: http://ji
[ http://jira.codehaus.org/browse/MRM-15?page=all ]
Brett Porter closed MRM-15:
---
Assign To: Brett Porter
Resolution: Fixed
this was in the old repoclean. I wrote it properly this time.
> partial POM written even on except
[ http://jira.codehaus.org/browse/MRM-15?page=comments#action_59289 ]
Edwin Punzalan commented on MRM-15:
---
Can you provide how to reproduce this? I did some revisions on the conversion
and I want to see if this still exist. Thanks.
> partial POM writ
[ http://jira.codehaus.org/browse/MRM-62?page=all ]
Edwin Punzalan closed MRM-62:
-
Resolution: Fixed
Closing this now as the proxy module is now able to read the following
maven-proxy configurations and incorporate it in its own configuration
[ http://jira.codehaus.org/browse/MRM-70?page=all ]
Brett Porter updated MRM-70:
Fix Version: (was: 1.0-alpha-1)
Remaining Estimate: (was: 8 hours)
Original Estimate: (was: 8 hours)
> Browse by Group/Artifact/Vers
[ http://jira.codehaus.org/browse/MRM-74?page=all ]
Edwin Punzalan closed MRM-74:
-
Resolution: Fixed
Patch applied. Thanks.
> Browse web user interface
> -
>
> Key: MRM-74
> URL: http://ji
[ http://jira.codehaus.org/browse/MRM-70?page=all ]
John Tolentino closed MRM-70:
-
Resolution: Duplicate
Code already exists (see MRM-74).
> Browse by Group/Artifact/Version
>
>
> Key: MRM-70
&g
[ http://jira.codehaus.org/browse/MRM-38?page=all ]
Edwin Punzalan closed MRM-38:
-
Resolution: Fixed
Correct patch applied this time. ^_^
> add a background task scheduler
> ---
>
> Key: MRM-38
>
[ http://jira.codehaus.org/browse/MRM-38?page=all ]
Edwin Punzalan reopened MRM-38:
---
Sorry, patched the wrong file.
> add a background task scheduler
> ---
>
> Key: MRM-38
> URL: http://ji
[ http://jira.codehaus.org/browse/MRM-38?page=all ]
Edwin Punzalan closed MRM-38:
-
Resolution: Fixed
Patch Applied. Thanks.
> add a background task scheduler
> ---
>
> Key: MRM-38
>
[ http://jira.codehaus.org/browse/MRM-14?page=comments#action_59199 ]
Edwin Punzalan commented on MRM-14:
---
I think the original should be retained because there are so many possibilities
on how this can be happening.
Then probably add a user triggered
[ http://jira.codehaus.org/browse/MRM-13?page=all ]
Edwin Punzalan closed MRM-13:
-
Resolution: Fixed
> utilise repository relocation information during conversion of an artif
[ http://jira.codehaus.org/browse/MRM-74?page=all ]
Brett Porter updated MRM-74:
Fix Version: 1.0-alpha-1
> Browse web user interface
> -
>
> Key: MRM-74
> URL: http://jira.codehaus.org/browse/MRM-74
[ http://jira.codehaus.org/browse/MRM-70?page=all ]
Brett Porter updated MRM-70:
Fix Version: 1.0-alpha-1
> Browse by Group/Artifact/Version
>
>
> Key: MRM-70
> URL: http://jira.codehaus.or
[ http://jira.codehaus.org/browse/MRM-81?page=all ]
Brett Porter updated MRM-81:
Fix Version: 1.0-alpha-1
> Search web user interface
> -
>
> Key: MRM-81
> URL: http://jira.codehaus.org/browse/MRM-81
[ http://jira.codehaus.org/browse/MRM-79?page=comments#action_59190 ]
Brett Porter commented on MRM-79:
-
ping
> Repository Interface web user interface
> ---
>
> Key: MRM-79
>
[ http://jira.codehaus.org/browse/MRM-14?page=all ]
Brett Porter updated MRM-14:
Fix Version: (was: 1.0-alpha-1)
> utilise repository relocation information to update dependenc
[ http://jira.codehaus.org/browse/MRM-11?page=all ]
Brett Porter updated MRM-11:
Fix Version: (was: 1.0-alpha-1)
> Security policy for uploads must be in place
>
>
> Key: MRM-11
>
[ http://jira.codehaus.org/browse/MRM-28?page=all ]
Brett Porter updated MRM-28:
Fix Version: (was: 1.0-alpha-1)
> sync shouldn't use file sizes as basis - updated checksums are not
[ http://jira.codehaus.org/browse/MRM-12?page=all ]
Brett Porter updated MRM-12:
Fix Version: (was: 1.0-alpha-1)
> POI directory structure incorrectly converted from m1 repo
> --
>
>
[ http://jira.codehaus.org/browse/MRM-10?page=all ]
Brett Porter updated MRM-10:
Fix Version: (was: 1.0-alpha-1)
> syncopate needs to validate the incoming directory layout
> -
>
>
[ http://jira.codehaus.org/browse/MRM-90?page=all ]
Brett Porter updated MRM-90:
Fix Version: (was: 1.0-alpha-1)
> add advanced search options
> ---
>
> Key: MRM-90
> URL: http://jira.codehaus.or
[ http://jira.codehaus.org/browse/MRM-58?page=all ]
Edwin Punzalan closed MRM-58:
-
Resolution: Fixed
Fixed along with MRM-57
> create a search result class for returning from sea
[ http://jira.codehaus.org/browse/MRM-57?page=all ]
Edwin Punzalan closed MRM-57:
-
Resolution: Fixed
> ability to retrieve matched portion of classes, packages and files fie
[ http://jira.codehaus.org/browse/MRM-69?page=all ]
Brett Porter updated MRM-69:
Fix Version: 1.0-alpha-1
> Simple "query everything" search
>
>
> Key: MRM-69
> URL: http://jira.c
[ http://jira.codehaus.org/browse/MRM-88?page=all ]
Brett Porter updated MRM-88:
Fix Version: 1.0-alpha-1
> search by filename
> --
>
> Key: MRM-88
> URL: http://jira.codehaus.org/browse/MRM-88
>
[ http://jira.codehaus.org/browse/MRM-68?page=all ]
Brett Porter updated MRM-68:
Fix Version: 1.0-alpha-1
> Accomodate "query everything" in the index
> --
>
> Key: MRM-6
[ http://jira.codehaus.org/browse/MRM-97?page=all ]
Brett Porter updated MRM-97:
Fix Version: 1.0-alpha-1
> Allow hard-fail configuration for a remote repository
> -
>
> Key: MRM-97
&g
[ http://jira.codehaus.org/browse/MRM-54?page=all ]
Brett Porter updated MRM-54:
Fix Version: 1.0-alpha-1
> allow nested search parameters
> --
>
> Key: MRM-54
> URL: http://jira.codehaus.or
[ http://jira.codehaus.org/browse/MRM-96?page=all ]
Brett Porter updated MRM-96:
Fix Version: 1.0-alpha-1
> Enable the use of http proxies when mrm is restricted to browse directly over
> t
1 - 100 of 441 matches
Mail list logo
