Re: [jira] Moved: (MRM-759) add a generic script for platforms that don't support the wrapper
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-759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter moved CONTINUUM-1707 to MRM-759:
-
Affects Version/s: (was: 1.2)
1.1
Key: MRM-759 (was: CONTINUUM-1707)
Project: Archiva (was: Continuum)
add a generic script for platforms that don't support the wrapper
-
Key: MRM-759
URL: http://jira.codehaus.org/browse/MRM-759
Project: Archiva
Issue Type: Improvement
Affects Versions: 1.1
Reporter: Brett Porter
Fix For: 1.1
using the new generated Jetty bundle, there is no way to start the
server (equivalent to plexus.sh) when the platform is not supported
by the
bundled scripts
--
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
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
Re: [jira] Moved: (MRM-759) add a generic script for platforms that don't support the wrapper
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 Porter moved CONTINUUM-1707 to MRM-759: > - > >Affects Version/s: (was: 1.2) > 1.1 > Key: MRM-759 (was: CONTINUUM-1707) > Project: Archiva (was: Continuum) > > > add a generic script for platforms that don't support the wrapper > > ----- > > > > Key: MRM-759 > > URL: http://jira.codehaus.org/browse/MRM-759 > > Project: Archiva > > Issue Type: Improvement > >Affects Versions: 1.1 > >Reporter: Brett Porter > > Fix For: 1.1 > > > > > > using the new generated Jetty bundle, there is no way to start the > server (equivalent to plexus.sh) when the platform is not supported by the > bundled scripts > > -- > 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 > > >
[MRM-594] updated
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.
Re: MRM-594/595/596
That's also my first choice, as I never used Jpox so it would be simplier for me ;-). 2007/11/16, Brett Porter <[EMAIL PROTECTED]>: > > 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 and m2 builds on our projects. > > > > On MRM-594 : where could we store custom "legacy path --> artifact" > > convertions ? Some new elements in archivaConfiguration ? Use new > > tables in > > archiva DB ? > > > > Nico. > > -- > Brett Porter - [EMAIL PROTECTED] > Blog: http://www.devzuz.org/blogs/bporter/ > >
Re: MRM-594/595/596
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 and m2 builds on our projects. On MRM-594 : where could we store custom "legacy path --> artifact" convertions ? Some new elements in archivaConfiguration ? Use new tables in archiva DB ? Nico. -- Brett Porter - [EMAIL PROTECTED] Blog: http://www.devzuz.org/blogs/bporter/
Re: [DISCUSS] [MRM-564] Audit Logging.
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 not sure about this one? 8) Auto-Remove Consumer 9) Auto-Rename Consumer 10) Snapshot Repository Purge Consumer sounds good - but happy for that to be filed as a new issue for the future (and include Wendy's additional comments about logging changes noticed during the scan) 11) Scan Start 12) Scan End already in the main log? Also, what should we use in the log field for "user id" and "remote ip" when logging from consumers? One idea would be to use "[consumer]" or "[purge]" style/format for the "user id" field, and "0.0.0.0" for remote ip in this situation. I'd just put N/A (or "-") in each field in that case, and add something meaningful to the action (automatically removed snapshot due as it was older than 90 days, etc). Cheers, Brett -- Brett Porter - [EMAIL PROTECTED] Blog: http://www.devzuz.org/blogs/bporter/
Re: [MRM-435] Need to review repository defaults
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 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. What kind of resolution is being proposed for this? I think this one can be closed. As ... 1) The logging has been updated. 2) The repositories screen shows a big fat red error box if the directory is invalid, can't be found, can't be created, or can't be written to. What else is there? -- - Joakim Erdfelt [EMAIL PROTECTED] Open Source Software (OSS) Developer -- Brett Porter - [EMAIL PROTECTED] Blog: http://www.devzuz.org/blogs/bporter/
[DISCUSS] [MRM-564] Audit Logging.
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}\""
Example output:
2007-11-08 11:18:43 internal joakim 127.0.0.1
"org/codehaus/plexus/plexus-utils/1.0.4/plexus-utils-1.0.4.jar" "Created
File (proxied)"
2007-11-08 11:18:43 internal joakim 127.0.0.1
"org/codehaus/plexus/plexus-compiler-manager/1.5.3/plexus-compiler-manager-1.5.3.jar"
"Created File (proxied)"
2007-11-08 11:19:00 internal joakim 127.0.0.1
"org/apache/maven/maven/2.0.6/maven-2.0.6.pom" "Created File (proxied)"
2007-11-08 11:19:01 internal joakim 127.0.0.1
"org/apache/maven/maven-settings/2.0.6/maven-settings-2.0.6.pom"
"Created File (proxied)"
2007-11-08 11:32:06 internal joakim 127.0.0.1 "/net" "Created Directory"
2007-11-08 11:32:06 internal joakim 127.0.0.1 "/net/erdfelt" "Created
Directory"
2007-11-08 11:32:06 internal joakim 127.0.0.1 "/net/erdfelt/sysutils"
"Created Directory"
2007-11-08 11:32:06 internal joakim 127.0.0.1
"/net/erdfelt/sysutils/1.1" "Created Directory"
2007-11-08 11:32:06 internal joakim 127.0.0.1
"/net/erdfelt/sysutils/1.1/sysutils-1.1.jar" "Created File"
2007-11-08 11:32:07 internal joakim 127.0.0.1
"/net/erdfelt/sysutils/1.1/sysutils-1.1.jar.md5" "Created File"
2007-11-08 11:32:07 internal joakim 127.0.0.1
"/net/erdfelt/sysutils/1.1/sysutils-1.1.jar.sha1" "Created File"
2007-11-08 11:32:08 internal joakim 127.0.0.1
"/net/erdfelt/sysutils/1.1/sysutils-1.1.pom" "Created File"
2007-11-08 11:32:08 internal joakim 127.0.0.1
"/net/erdfelt/sysutils/1.1/sysutils-1.1.pom.md5" "Created File"
2007-11-08 11:32:08 internal joakim 127.0.0.1
"/net/erdfelt/sysutils/1.1/sysutils-1.1.pom.sha1" "Created File"
2007-11-08 11:32:09 internal joakim 127.0.0.1
"/net/erdfelt/sysutils/maven-metadata.xml" "Created File"
2007-11-08 11:32:09 internal joakim 127.0.0.1
"/net/erdfelt/sysutils/maven-metadata.xml.md5" "Created File"
2007-11-08 11:32:09 internal joakim 127.0.0.1
"/net/erdfelt/sysutils/maven-metadata.xml.sha1" "Created File"
This is hooked up into the ProxiedDavServer component at the moment, but
in a discussion with Wendy on irc, I identified a few more potential
places to generate audit log from ...
1) Repository Configuration Create
2) Repository Configuration Edit
3) Repository Configuration Delete
4) Proxy Connector Create
5) Proxy Connector Edit
6) Proxy Connector Delete
7) Metadata Merge
8) Auto-Remove Consumer
9) Auto-Rename Consumer
10) Snapshot Repository Purge Consumer
11) Scan Start
12) Scan End
We both agreed that #10 (Snapshot Repository Purge Consumer) is an
obvious one to hook up.
What are the feelings of the rest of developers and users of archiva?
What else should be logged?
What kind of guidelines should be placed on audit logging?
Also, what should we use in the log field for "user id" and "remote ip"
when logging from consumers?
One idea would be to use "[consumer]" or "[purge]" style/format for the
"user id" field, and "0.0.0.0" for remote ip in this situation.
Comments?
--
- Joakim Erdfelt
[EMAIL PROTECTED]
Open Source Software (OSS) Developer
[MRM-435] Need to review repository defaults
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 believe there is insufficient error handling to correct this situation if the user forgets to first set the variables during installation. What kind of resolution is being proposed for this? I think this one can be closed. As ... 1) The logging has been updated. 2) The repositories screen shows a big fat red error box if the directory is invalid, can't be found, can't be created, or can't be written to. What else is there? -- - Joakim Erdfelt [EMAIL PROTECTED] Open Source Software (OSS) Developer
Re: MRM-549 & MRM-547 : Proxy Connector Policy settings.
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 release and snapshots (it was an eg, not an ie). For cache: it's a yes/no answer, and for checksum ignore is valid. What about using SKIP in place of IGNORED? What about using REJECT in place of DISABLED? I'm still confused what that really means. In the first set, to me, SKIP means "don't ever check for updates", since the context is when to check for updates, right? But I think you're saying it means "skip the check about whether to check for updates and check for updates anyway". If the question to be asked is "how often should Archiva check for updates"? SKIP, DISABLED, IGNORED, REJECT are not valid answers in the context of what happens. ALWAYS and NEVER would be. Or am I asking the wrong question? If so, what is a question you can ask and have each option as an answer for that matches the current behaviour? Likewise: * Should I cache failures? YES or NO. Or it could be "What should I do when I encounter a failure?" CACHE or DON'T CACHE. But IGNORED/SKIP/DISABLED/REJECT don't make sense in this context (at least with the given behaviour) * What should I do when a checksum is invalid? IGNORE, FIX or FAIL. Make sense? No. Making no common ground between the options is also confusing. There needs to be a common "DO NOT USE" or "IGNORED" option. But I can release that opinion in favor of a clear and defined set of values. So far, all I'm getting is handwaving, big picture stuff, not a defined, concrete, list to work off of. As I intepret your last comments, I see the list now as the following ... Releases (old) IGNORED, ONCE, HOURLY, DAILY, DISABLED (proposed) SKIP, ONCE, HOURLY, DAILY, REJECT Snapshots (old) IGNORED, ONCE, HOURLY, DAILY, DISABLED (new) SKIP, ONCE, HOURLY, DAILY, REJECT Cache-Failures (old) IGNORED, CACHED (new) NO, YES Checksum (old) IGNORED, FIX, FAIL (new) SKIP, FIX, FAIL Any more changes? - Joakim
Re: MRM-549 & MRM-547 : Proxy Connector Policy settings.
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. Releases (old) IGNORED, ONCE, HOURLY, DAILY, DISABLED (new) ALWAYS, ONCE, HOURLY, DAILY, DISABLED Snapshots (old) IGNORED, ONCE, HOURLY, DAILY, DISABLED (new) ALWAYS, ONCE, HOURLY, DAILY, DISABLED Cache-Failures (old) IGNORED, CACHED (new) ALWAYS, CACHED Checksum (old) IGNORED, FIX, FAIL (new) ALWAYS, FIX, FAIL Using the logic that we should use wording that applies the artifact, (which itself is misleading, as these affect metadata too), then the DISABLED option should be changed too. I have a feeling that we are confusing the meanings of IGNORED and DISABLED. What about using SKIP in place of IGNORED? What about using REJECT in place of DISABLED? So it would become Releases (old) IGNORED, ONCE, HOURLY, DAILY, DISABLED (proposed) SKIP, ONCE, HOURLY, DAILY, REJECT Snapshots (old) IGNORED, ONCE, HOURLY, DAILY, DISABLED (new) SKIP, ONCE, HOURLY, DAILY, REJECT Cache-Failures (old) IGNORED, CACHED (new) SKIP, CACHED Checksum (old) IGNORED, FIX, FAIL (new) SKIP, FIX, FAIL WDYT? - Joakim Brett Porter wrote: I'd say 2) please just change "ignored" to a value that interacts with the artifact (eg, always) instead of the policy, since that's what all the other values do. On 23/10/2007, at 1:17 PM, Joakim Erdfelt 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 : proxy connectors: cache failures options are confusing http://docs.codehaus.org/display/MAVENUSER/Archiva+Proxy+Policies I'd like to hear from you about what is bad about the current settings? What is good about the current settings? Some options on how to correct this? (my 2 bits) 1) Create a sidebar on the proxy connector screen detailing the meaning of the policy settings. 2) Change the policy setting values to make more sense to the largest body of individuals. I'd like to get these closed out, it'll be a simple fix, but the decision needs discussion first. -- - Joakim Erdfelt [EMAIL PROTECTED] -- Brett Porter - [EMAIL PROTECTED] Blog: http://www.devzuz.org/blogs/bporter/
Re: MRM-462 progress
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 thought it could be (at least partially) contentious, and is at least quite disruptive. I won't have a problem merging the lot down to trunk once completed. Please review the changes if you are interested in it - I'm confident that the changes outside the webapp are solid since all the tests are passing again (I've added some coverage that was missing in archiva-configuration, the rest are much less consequential changes). The next step is to change the webapp, and I'l be adding tests there to ensure that the functionality is working. This could take a little longer. I'm worried at how much the implementation details of the configuration have leaked out throughout the application - something to review later on. Thanks, Brett -- Brett Porter - [EMAIL PROTECTED] Blog: http://www.devzuz.org/blogs/bporter/
Re: Progress on MRM-463 - Metadata support
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 trunk, the following changes have been made.
archiva-repository-layer:
[NEW] MetadataTools component that is responsible for the merging
and updating of inplace maven-metadata.xml files.
archiva-proxy:
[Update] DefaultProxyConnector now will ...
1) download requested maven-metadata.xml from *all* remote
repositories.
NOTE: must pass the pre-download policies first.
2) Save the downloaded maven-metadata.xml next to the
maven-metadata.xml that exists in the managed repository using a
filename format of maven-metadata-${proxyId}.xml (similar to how the
maven 2 local repository works now).
3) After all of the downloads from all proxied repositories
complete, a MetadataTools.updateMetadata() call is issued to perform
an update on that maven-metadata.xml file.
4) Upon a completion of the MetadataTools.updateMetadata() with no
error, the maven-metadata.xml file in the managed repository is
returned to the requesting client.
What's left.
archiva-core-consumers:
[NEW] MetadataUpdaterConsumer - which runs as part of the repository
scanning process and updates all of the in-place maven-metadata.xml
files.
Alsø Alsø Wik: I'm only mildly worried about Concurrency issues with
this solution, as most calls for the maven-metadata.xml will be
caught by the pre-download policies, and updates to those files will
occur only on occasion.
Feel free to rip my logic to shreds and tell me what an idiot I am.
(it's really the only way I'll learn) :-)
- Joakim
--
Brett Porter - [EMAIL PROTECTED]
Blog: http://www.devzuz.org/blogs/bporter/
I've tried out the proxying and checked out the metadata merging stuff
today, they both worked smoothly for me :)
Great work Joakim! :-)
-Deng
Re: MRM-462 progress
hehe - to be clear, I was kind of joking. My stuff is on a branch because I don't like local changes and because it isn't yet 100% working. I don't want to interfere with the release. It's existence will also help Joakim to review it and understand where there are potential conflicts, and minimise the damage. Right, Joakim? :) I don't intend to maintain it any longer than this week. On 21/08/2007, at 3:10 PM, Arnaud HERITIER wrote: It's why I'm not in favor of the decision we made to use branches. First times it could be a game. Following times it's quickly the war. The one who want to be the first to back home (in a corporate env) will commit its code with less checks and the last one will be punished by having to merge others changes. In opensource we are less in a hurry, thus I hope we'll not see the second case happen. 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 wrote: I have a decent raft of new code coming in as part of MRM-463 (metadata stuff), can you hold off until that commit comes in? - Joakim Brett Porter wrote: I decided to use a branch for the configuration split since I thought it could be (at least partially) contentious, and is at least quite disruptive. I won't have a problem merging the lot down to trunk once completed. Please review the changes if you are interested in it - I'm confident that the changes outside the webapp are solid since all the tests are passing again (I've added some coverage that was missing in archiva-configuration, the rest are much less consequential changes). The next step is to change the webapp, and I'l be adding tests there to ensure that the functionality is working. This could take a little longer. I'm worried at how much the implementation details of the configuration have leaked out throughout the application - something to review later on. Thanks, Brett -- .. Arnaud HERITIER .. OCTO Technology - aheritier AT octo DOT com www.octo.com | blog.octo.com .. ASF - aheritier AT apache DOT org www.apache.org | maven.apache.org ...
Re: MRM-462 progress
It's why I'm not in favor of the decision we made to use branches. First times it could be a game. Following times it's quickly the war. The one who want to be the first to back home (in a corporate env) will commit its code with less checks and the last one will be punished by having to merge others changes. In opensource we are less in a hurry, thus I hope we'll not see the second case happen. 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 wrote: > > > I have a decent raft of new code coming in as part of MRM-463 > > (metadata stuff), can you hold off until that commit comes in? > > > > - Joakim > > > > Brett Porter wrote: > >> I decided to use a branch for the configuration split since I > >> thought it could be (at least partially) contentious, and is at > >> least quite disruptive. I won't have a problem merging the lot > >> down to trunk once completed. > >> > >> Please review the changes if you are interested in it - I'm > >> confident that the changes outside the webapp are solid since all > >> the tests are passing again (I've added some coverage that was > >> missing in archiva-configuration, the rest are much less > >> consequential changes). > >> > >> The next step is to change the webapp, and I'l be adding tests > >> there to ensure that the functionality is working. This could take > >> a little longer. > >> > >> I'm worried at how much the implementation details of the > >> configuration have leaked out throughout the application - > >> something to review later on. > >> > >> Thanks, > >> Brett > >> > -- .. Arnaud HERITIER .. OCTO Technology - aheritier AT octo DOT com www.octo.com | blog.octo.com .. ASF - aheritier AT apache DOT org www.apache.org | maven.apache.org ...
Re: Repository purge (MRM-294 and MRM-275)
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 schedule and set up as another consumer which would be executed during repository scanning. I think you and Brett have worked out the details, so I just want to confirm that this will be configurable in archiva.xml prior to starting the app. Yep, it'll be configurable in archiva.xml :) Thanks, Deng
Re: Repository purge (MRM-294 and MRM-275)
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 more than 5. If the total number of that snapshot in the repo didn't reach 5, then it would keep all of them. I think we're saying the same thing - can you just clarify for me are you saying 5 are: a) 1.1-SNAPSHOT, 1.2-SNAPSHOT, 1.3-SNAPSHOT, 1.4-SNAPSHOT, 1.5-SNAPSHOT; or b) 1.1-20070506.121113-1, 1.1-20070506.121113-2, 1.1-20070506.121113-3, 1.1-20070506.121113-4, 1.1-20070506.121113-5 I was thinking it's (b), since (a) is taken care of by the "delete anything that's released" rule. Cheers, Brett
Re: MRM-212 - work in progress ?
Sorry Nicolas, I didn't advance a lot on this problem. I'm always using at work my old snapshot of archiva because I have some others issues with the newest. I'll keep you informed if I have the time to work on it shortly. Arnaud On 04/04/07, nicolas de loof <[EMAIL PROTECTED]> 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.
MRM-212 - work in progress ?
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.
Re: [vote] merge Archiva MRM-239 branch to trunk
+1 I'm not done, but I can't see any issues at a high level. I'll post any thoughts I have later. - Brett On 23/02/2007, at 7:54 PM, Brett Porter wrote: Applying them now won't help... they'd still need to painstakingly be applied to the branch. Just as easy to do that after the merge (if they are still relevant). I believe some things on trunk may have changed since the last merge - a final check of that will be needed first. I'm still reviewing the code, myself... vote to arrive later tonight :) - Brett On 23/02/2007, at 7:49 PM, Arnaud HERITIER wrote: 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) ? 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 > > >
Re: [vote] merge Archiva MRM-239 branch to trunk
With the following voters in favor ... Brett, Arnaud, Emmanuel, Nicolas ... the merge will commence shortly - Joakim Brett Porter wrote: > +1 > > I'm not done, but I can't see any issues at a high level. I'll post > any thoughts I have later. > > - Brett > > On 23/02/2007, at 7:54 PM, Brett Porter wrote: > >> Applying them now won't help... they'd still need to painstakingly be >> applied to the branch. Just as easy to do that after the merge (if >> they are still relevant). >> >> I believe some things on trunk may have changed since the last merge >> - a final check of that will be needed first. >> >> I'm still reviewing the code, myself... vote to arrive later tonight :) >> >> - Brett >> >> On 23/02/2007, at 7:49 PM, Arnaud HERITIER wrote: >> >>> 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) ? >>> >>> 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 >>>> > >>>> > >>>> > >>>> >>>> >
Re: [vote] merge Archiva MRM-239 branch to trunk
Applying them now won't help... they'd still need to painstakingly be applied to the branch. Just as easy to do that after the merge (if they are still relevant). I believe some things on trunk may have changed since the last merge - a final check of that will be needed first. I'm still reviewing the code, myself... vote to arrive later tonight :) - Brett On 23/02/2007, at 7:49 PM, Arnaud HERITIER wrote: 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) ? 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 > > >
Re: [vote] merge Archiva MRM-239 branch to trunk
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) ? 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 > > >
Re: [vote] merge Archiva MRM-239 branch to trunk
+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
Re: [vote] merge Archiva MRM-239 branch to trunk
+1 I'm using archiva snapshot as a maven1&2 proxy to repo1.apache.org. I entoutered the OutOfMemory issue and had to setup a cron to stop/restart tomcat every night. 2007/2/22, Arnaud HERITIER <[EMAIL PROTECTED]>: +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 >
Re: [vote] merge Archiva MRM-239 branch to trunk
+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
Re: [jira] Closed: (MRM-283) Password Length too Short
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't fix", "incomplete" or "cannot reproduce" I actually wanted to resolve it as "Not a Problem" but we don't seem to have it in this project... Fixed was closer to the truth than any of the other options. I intentionally left the 'fix version' blank so it shouldn't appear in the release notes. At least, that was the intention. :) -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [jira] Closed: (MRM-283) Password Length too Short
Hi Wendy, 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't 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. --- Resolution: Fixed > Password Length too Short > - > > Key: MRM-283 > URL: http://jira.codehaus.org/browse/MRM-283 > Project: Archiva > Issue Type: Improvement > Components: Users/Security >Affects Versions: 1.0 >Reporter: Robert Simmons Jr. > > An 8 character password is far too short for good security. Can we improve this to a 16 character password? -- 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 -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: MRM-153 (archiva to handle relocation for maven1 clients)
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 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) > 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. Solving this has two options : > > - build the path from the returned File (requires some > getAbsolutePath().substring() that are not very clean). Perhaps there is > methods to get the path of the artifact based on the File object ? > - change proxyRequestHandler to return a path and not a File (or some > composite object) > > What do you think would be better ? > > Nico. >
Re: MRM-153 (archiva to handle relocation for maven1 clients)
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) > 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. Solving this has two options : > > - build the path from the returned File (requires some > getAbsolutePath().substring() that are not very clean). Perhaps there is > methods to get the path of the artifact based on the File object ? > - change proxyRequestHandler to return a path and not a File (or some > composite object) > > What do you think would be better ? > > Nico. >
MRM-153 (archiva to handle relocation for maven1 clients)
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. Solving this has two options : - build the path from the returned File (requires some getAbsolutePath().substring() that are not very clean). Perhaps there is methods to get the path of the artifact based on the File object ? - change proxyRequestHandler to return a path and not a File (or some composite object) What do you think would be better ? Nico.
(MRM-224) Wrong extension for M1 plugins on repo conversion
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 requires to run a patched repo-converter on maven public repository to be solved. Nico. This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
Re: Artifact/Dependency details in MPIR and MRM
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 going thought the list of dependencies, it seems kind of silly that all maven artifacts share the same description. Doesn't really make a good example. Milos On 8/11/06, Joakim Erdfelt <[EMAIL PROTECTED]> wrote: I just uploaded MPIR-55 which adds dependency details and dependency repository location sections to the dependencies report. See the last two sections on this example report - http://joakim.erdfelt.com/maven-project-info-reports-plugin/dependencies.html It uses a new module called maven-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 a Sealed Jar. (make the user consider an older version that uses JDK 1.4 instead) Would anyone else find this useful for MRM? I can imagine custom searches that utilize this information too. "wagon jdk:<1.4" or "commons-beanutils jdk:<1.5 debug:true" as some example searches. - Joakim Erdfelt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Artifact/Dependency details in MPIR and MRM
I just uploaded MPIR-55 which adds dependency details and dependency repository location sections to the dependencies report. See the last two sections on this example report - http://joakim.erdfelt.com/maven-project-info-reports-plugin/dependencies.html It uses a new module called maven-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 a Sealed Jar. (make the user consider an older version that uses JDK 1.4 instead) Would anyone else find this useful for MRM? I can imagine custom searches that utilize this information too. "wagon jdk:<1.4" or "commons-beanutils jdk:<1.5 debug:true" as some example searches. - Joakim Erdfelt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: MRM Build Broken
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-application-1.0-SNAPSHOT.jar to C:\Documents and Settings\dbeckedorff\.m2\re pository\org\apache\maven\repository\maven-repository-application\1.0-SNAPSH OT\maven-reposit ory-application-1.0-SNAPSHOT.jar [INFO] [INFO] Building Maven Repository Manager Artifact Applet [INFO]task-segment: [install] [INFO] [INFO] [ERROR] BUILD ERROR [INFO] [INFO] 'sign' was specified in an execution, but not found in the plugin [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: 'sign' was specified in an execution , but not found in the plugin at org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindExecutionToLifecycle (Defa ultLifecycleExecutor.java:1337) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindPluginToLifecycle(De fault LifecycleExecutor.java:1238) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappin gs(De faultLifecycleExecutor.java:982) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifec ycleE xecutor.java:453) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFail ures( DefaultLifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(Defa ultLi fecycleExecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycle Execu tor.java:140) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39 ) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl .java :25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) [INFO] [INFO] Total time: 37 seconds [INFO] Finished at: Mon Jun 12 13:43:29 EDT 2006 [INFO] Final Memory: 9M/17M [INFO] <<< ___ David Beckedorff Senior Developer CellExchange, Inc. [EMAIL PROTECTED] Office: (617)528-2196 Cell: (781)820-0567 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
MRM Build Broken
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\repository\maven-repository-application\1.0-SNAPSH OT\maven-reposit ory-application-1.0-SNAPSHOT.jar [INFO] [INFO] Building Maven Repository Manager Artifact Applet [INFO]task-segment: [install] [INFO] [INFO] [ERROR] BUILD ERROR [INFO] [INFO] 'sign' was specified in an execution, but not found in the plugin [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: 'sign' was specified in an execution , but not found in the plugin at org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindExecutionToLifecycle (Defa ultLifecycleExecutor.java:1337) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindPluginToLifecycle(De fault LifecycleExecutor.java:1238) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappin gs(De faultLifecycleExecutor.java:982) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifec ycleE xecutor.java:453) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFail ures( DefaultLifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(Defa ultLi fecycleExecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycle Execu tor.java:140) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39 ) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl .java :25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) [INFO] [INFO] Total time: 37 seconds [INFO] Finished at: Mon Jun 12 13:43:29 EDT 2006 [INFO] Final Memory: 9M/17M [INFO] <<< ___ David Beckedorff Senior Developer CellExchange, Inc. [EMAIL PROTECTED] Office: (617)528-2196 Cell: (781)820-0567
MRM
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 Senior Developer CellExchange, Inc. [EMAIL PROTECTED] Office: (617)528-2196 Cell: (781)820-0567
Re: MRM pointers
I actually haven't played with the combined webapp yet, just the initial prototype I put together and the individual components. I'm not sure if the indexing was wired up automatically. There is an indexing CLI you might be able to use in the -application module to create the index 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, and create some directories on /tmp/MRM (which is the path I've > chosen on plexus.xml). Now, the issues > > 1. When I tried to search for an artefact, I got one exception > regaring the /tmp/MRM/index/directory. I solved it by copying the > directory target/index to /tmp/MRM, but I'm not sure if that's the > right option. > 2.Now the search works, but it doesn't find anything; I've tried to > copy my $HOME/.m2 to /tmp/MRM, but it didn't work neither > 3.Finally, I realized there is a proxy-cache directory on target as > well - should I do something about it? > > I know the project is still on early stages of development so it's > lacking documentation, but if you could provide at least a quick-start > guide, I could try to use it (and eventually help fixing the issues > :-) > > -- Felipe > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
MRM pointers
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 plexus.xml). Now, the issues 1. When I tried to search for an artefact, I got one exception regaring the /tmp/MRM/index/directory. I solved it by copying the directory target/index to /tmp/MRM, but I'm not sure if that's the right option. 2.Now the search works, but it doesn't find anything; I've tried to copy my $HOME/.m2 to /tmp/MRM, but it didn't work neither 3.Finally, I realized there is a proxy-cache directory on target as well - should I do something about it? I know the project is still on early stages of development so it's lacking documentation, but if you could provide at least a quick-start guide, I could try to use it (and eventually help fixing the issues :-) -- Felipe - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Bulding MRM
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 > deployed a new snapshot - hopefully this willl make it build out of the > box. > >
Re: Bulding MRM
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 1.4, Maven 2.0.3. > > Summary: > > [INFO] Building Maven Repository Manager Artifact Applet > [INFO]task-segment: [install] > [INFO] > > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] 'sign' was specified in an execution, but not found in the plugin > [INFO] > > [INFO] Trace > org.apache.maven.lifecycle.LifecycleExecutionException: 'sign' was > specified in an execution, but not found in the plugin > > Full text: > > http://www.rafb.net/paste/results/pUouHi48.html > > > > Any thoughts? > > Hen > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Bulding MRM
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] [INFO] [ERROR] BUILD ERROR [INFO] [INFO] 'sign' was specified in an execution, but not found in the plugin [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: 'sign' was specified in an execution, but not found in the plugin Full text: http://www.rafb.net/paste/results/pUouHi48.html Any thoughts? Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: MRM and Bytecode Hash.
+1, with comments :) Is this just bytecode (ie, classfiles), or is it a hash of the contents of all files? The latter sounds good for arbitrary zip files (and other archives when supported). Cheers, Brett Joakim Erdfelt wrote: > I would like to see a new hash technique be added to the index. > > 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 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 technique in a small > maven project located at http://joakim.erdfelt.com/truehash.tar.gz > > I am willing to implement a patch for this. > > - Joakim > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
MRM and Bytecode Hash.
I would like to see a new hash technique be added to the index. 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 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 technique in a small maven project located at http://joakim.erdfelt.com/truehash.tar.gz I am willing to implement a patch for this. - Joakim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MRM-99) Use RepositoryIndexSearchLayer for searching in Packages
[ http://jira.codehaus.org/browse/MRM-99?page=all ] Edwin Punzalan closed MRM-99: - Resolution: Fixed Patch applied. Thanks. > 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-alpha-1 > Reporter: John Tolentino > Assignee: Maria Odea Ching > Attachments: MRM-99-maven-repository-webapp.patch > > Time Spent: 30 minutes >Remaining: 0 minutes > > Update PackageSearchAction to use RepositoryIndexSearchLayer and change > search result page to use SearchResult class. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MRM-32) Repository Indexing
[ 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 > --- > > Key: MRM-32 > URL: http://jira.codehaus.org/browse/MRM-32 > Project: Maven Repository Manager > Type: New Feature > Components: indexing > Reporter: Brett Porter > Assignee: Maria Odea Ching > Fix For: 1.0-alpha-1 > > > Create a repository indexer using Lucene -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-99) Use RepositoryIndexSearchLayer for searching in Packages
[ 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 Packages > > > Key: MRM-99 > URL: http://jira.codehaus.org/browse/MRM-99 > Project: Maven Repository Manager > Type: Bug > Components: web application > Versions: 1.0-alpha-1 > Reporter: John Tolentino > Attachments: MRM-99-maven-repository-webapp.patch > > Time Spent: 30 minutes >Remaining: 0 minutes > > Update PackageSearchAction to use RepositoryIndexSearchLayer and change > search result page to use SearchResult class. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MRM-98) Use the plexus configuration for index and repository path
[ 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 path > -- > > Key: MRM-98 > URL: http://jira.codehaus.org/browse/MRM-98 > Project: Maven Repository Manager > Type: Improvement > Components: web application > Versions: 1.0-alpha-1 > Reporter: John Tolentino > Assignee: John Tolentino > Attachments: maven-repository-webapp.diff > > > Use same plexus configuration code in GeneralSearch for PackageSearchAction. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MRM-99) Use RepositoryIndexSearchLayer for searching in Packages
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-alpha-1 Reporter: John Tolentino Update PackageSearchAction to use RepositoryIndexSearchLayer and change search result page to use SearchResult class. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MRM-98) Use the plexus configuration for index and repository path
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 Versions: 1.0-alpha-1 Reporter: John Tolentino Attachments: maven-repository-webapp.diff Use same plexus configuration code in GeneralSearch for PackageSearchAction. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MRM-36) integration with discovery and scheduling
[ 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 > URL: http://jira.codehaus.org/browse/MRM-36 > Project: Maven Repository Manager > Type: Sub-task > Components: indexing > Reporter: Brett Porter > Assignee: Maria Odea Ching > Fix For: 1.0-alpha-1 > Attachments: MRM-36-maven-repository-webapp.patch > > Original Estimate: 15 hours >Time Spent: 23 hours > Remaining: 0 minutes > > I presume the regular indexer will process an individual file and add it to > the index, or remove a file from the index. This should integrated with the > discovery mechanism so that it can trigger the indexing of files (or removal > - though this is not currently in the discovery mechanism). > As for scheduling, it may be that the index updates are processed on a > scheduled interval so that integration might be needed. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MRM-42) discover repository metadata
[ 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://jira.codehaus.org/browse/MRM-42 > Project: Maven Repository Manager > Type: Task > Components: discovery > Reporter: Brett Porter > Assignee: Maria Odea Ching > Fix For: 1.0-alpha-1 > Attachments: MRM-42-maven-repository-discovery.patch, > MRM-42-repository-manager-discovery.patch, > MRM-42-repository-manager-discovery.patch > > Original Estimate: 18 hours >Time Spent: 18 hours > Remaining: 0 minutes > -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-36) integration with discovery and scheduling
[ 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 > - > > Key: MRM-36 > URL: http://jira.codehaus.org/browse/MRM-36 > Project: Maven Repository Manager > Type: Sub-task > Components: indexing > Reporter: Brett Porter > Assignee: Maria Odea Ching > Fix For: 1.0-alpha-1 > Attachments: MRM-36-maven-repository-webapp.patch > > Original Estimate: 15 hours >Time Spent: 7 hours > Remaining: 8 hours > > I presume the regular indexer will process an individual file and add it to > the index, or remove a file from the index. This should integrated with the > discovery mechanism so that it can trigger the indexing of files (or removal > - though this is not currently in the discovery mechanism). > As for scheduling, it may be that the index updates are processed on a > scheduled interval so that integration might be needed. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-42) discover repository metadata
[ 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 > URL: http://jira.codehaus.org/browse/MRM-42 > Project: Maven Repository Manager > Type: Task > Components: discovery > Reporter: Brett Porter > Assignee: Maria Odea Ching > Fix For: 1.0-alpha-1 > Attachments: MRM-42-maven-repository-discovery.patch, > MRM-42-repository-manager-discovery.patch, > MRM-42-repository-manager-discovery.patch > > Original Estimate: 18 hours >Time Spent: 18 hours > Remaining: 0 minutes > -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Reopened: (MRM-42) discover repository metadata
[ 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 > > > Key: MRM-42 > URL: http://jira.codehaus.org/browse/MRM-42 > Project: Maven Repository Manager > Type: Task > Components: discovery > Reporter: Brett Porter > Assignee: Maria Odea Ching > Fix For: 1.0-alpha-1 > Attachments: MRM-42-repository-manager-discovery.patch, > MRM-42-repository-manager-discovery.patch > > Original Estimate: 18 hours >Time Spent: 18 hours > Remaining: 0 minutes > -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MRM-81) Search web user interface
[ 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://jira.codehaus.org/browse/MRM-81 > Project: Maven Repository Manager > Type: Task > Components: web application > Versions: 1.0-alpha-1 > Reporter: John Tolentino > Assignee: John Tolentino > Fix For: 1.0-alpha-1 > Attachments: MRM-81-maven-repository-indexer.diff, > MRM-81-maven-repository-webapp.diff > > Original Estimate: 16 hours >Time Spent: 14 hours > Remaining: 2 hours > > General search page and search result page. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-81) Search web user interface
[ 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://jira.codehaus.org/browse/MRM-81 > Project: Maven Repository Manager > Type: Task > Components: web application > Versions: 1.0-alpha-1 > Reporter: John Tolentino > Assignee: John Tolentino > Fix For: 1.0-alpha-1 > Attachments: MRM-81-maven-repository-indexer.diff, > MRM-81-maven-repository-webapp.diff > > Original Estimate: 16 hours >Time Spent: 14 hours > Remaining: 2 hours > > General search page and search result page. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-81) Search web user interface
[ 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 > URL: http://jira.codehaus.org/browse/MRM-81 > Project: Maven Repository Manager > Type: Task > Components: web application > Versions: 1.0-alpha-1 > Reporter: John Tolentino > Assignee: John Tolentino > Fix For: 1.0-alpha-1 > Attachments: MRM-81-maven-repository-indexer.diff, > MRM-81-maven-repository-webapp.diff > > Original Estimate: 16 hours >Time Spent: 14 hours > Remaining: 2 hours > > General search page and search result page. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-81) Search web user interface
[ 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://jira.codehaus.org/browse/MRM-81 > Project: Maven Repository Manager > Type: Task > Components: web application > Versions: 1.0-alpha-1 > Reporter: John Tolentino > Assignee: John Tolentino > Fix For: 1.0-alpha-1 > Attachments: MRM-81-maven-repository-indexer.diff, > MRM-81-maven-repository-webapp.diff > > Original Estimate: 16 hours >Time Spent: 6 hours > Remaining: 10 hours > > General search page and search result page. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-81) Search web user interface
[ 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://jira.codehaus.org/browse/MRM-81 > Project: Maven Repository Manager > Type: Task > Components: web application > Versions: 1.0-alpha-1 > Reporter: John Tolentino > Assignee: John Tolentino > Fix For: 1.0-alpha-1 > Attachments: MRM-81-maven-repository-indexer.diff > > Original Estimate: 16 hours >Time Spent: 6 hours > Remaining: 10 hours > > General search page and search result page. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MRM-91) create a second index with a subset of information, and have it compressed
[ 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 compressed > -- > > Key: MRM-91 > URL: http://jira.codehaus.org/browse/MRM-91 > Project: Maven Repository Manager > Type: New Feature > Components: indexing > Reporter: Brett Porter > Assignee: Edwin Punzalan > Fix For: 1.0-alpha-1 > > Original Estimate: 8 hours > Remaining: 8 hours > > required for the eclipse plugin. Will need to follow up with Jason on exactly > what data is required. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-91) create a second index with a subset of information, and have it compressed
[ 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 created for the eclipse plugin > create a second index with a subset of information, and have it compressed > -- > > Key: MRM-91 > URL: http://jira.codehaus.org/browse/MRM-91 > Project: Maven Repository Manager > Type: New Feature > Components: indexing > Reporter: Brett Porter > Assignee: Edwin Punzalan > Fix For: 1.0-alpha-1 > > Original Estimate: 8 hours > Remaining: 8 hours > > required for the eclipse plugin. Will need to follow up with Jason on exactly > what data is required. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MRM-41) discover standalone POMs
[ 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 > URL: http://jira.codehaus.org/browse/MRM-41 > Project: Maven Repository Manager > Type: Task > Components: discovery > Reporter: Brett Porter > Assignee: John Tolentino > Fix For: 1.0-alpha-1 > Attachments: MRM-41-maven-repository-discovery.diff, > MRM-41-maven-repository-discovery.diff, > MRM-41-maven-repository-discovery.diff, repository-manager.diff > > Time Spent: 21 hours >Remaining: 0 minutes > > where the pom is the artifact -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Reopened: (MRM-41) discover standalone POMs
[ 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 standalone POMs > > > Key: MRM-41 > URL: http://jira.codehaus.org/browse/MRM-41 > Project: Maven Repository Manager > Type: Task > Components: discovery > Reporter: Brett Porter > Assignee: John Tolentino > Fix For: 1.0-alpha-1 > Attachments: MRM-41-maven-repository-discovery.diff, > MRM-41-maven-repository-discovery.diff, > MRM-41-maven-repository-discovery.diff, repository-manager.diff > > Time Spent: 21 hours >Remaining: 0 minutes > > where the pom is the artifact -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MRM-59) Proxy should work transparently with either maven 1.x or 2.x repositories.
[ 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 repositories. > -- > > Key: MRM-59 > URL: http://jira.codehaus.org/browse/MRM-59 > Project: Maven Repository Manager > Type: New Feature > Components: remote proxy > Reporter: Tim Clemons > Assignee: Edwin Punzalan > Fix For: 1.0-alpha-1 > > Original Estimate: 12 hours > Remaining: 12 hours > > Have the maven-proxy act as either a maven 1.x or maven 2.x repository, > depending on which client accesses it. Brett believed this should be > managable with aliasing. > This was originally posted as a maven-proxy feature at > http://jira.codehaus.org/browse/MAVENPROXY-39 -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-40) associate artifacts with their pom and checksums
[ 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 > > > Key: MRM-40 > URL: http://jira.codehaus.org/browse/MRM-40 > Project: Maven Repository Manager > Type: Task > Components: discovery > Reporter: Brett Porter > Assignee: Brett Porter > Fix For: 1.0-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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MRM-59) Proxy should work transparently with either maven 1.x or 2.x repositories.
[ 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 already handles working with remote repositories of any format by taking the artifact and converting it to the correct layout, right? - the proxy servlet would be configured so that /proxy-m1/* maps to the proxy servlet with path format = legacy. So a path under there would be groupId/types/artifactId-version.ext - the proxy servlet would be configured so that /proxy-m2/* maps to the proxy servlet with path format = default. So a path under there would be groupId/artifactId/version/artifactId-version.ext > Proxy should work transparently with either maven 1.x or 2.x repositories. > -- > > Key: MRM-59 > URL: http://jira.codehaus.org/browse/MRM-59 > Project: Maven Repository Manager > Type: New Feature > Components: remote proxy > Reporter: Tim Clemons > Assignee: Edwin Punzalan > Fix For: 1.0-alpha-1 > > Original Estimate: 12 hours > Remaining: 12 hours > > Have the maven-proxy act as either a maven 1.x or maven 2.x repository, > depending on which client accesses it. Brett believed this should be > managable with aliasing. > This was originally posted as a maven-proxy feature at > http://jira.codehaus.org/browse/MAVENPROXY-39 -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-59) Proxy should work transparently with either maven 1.x or 2.x repositories.
[ 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 repositories. > -- > > Key: MRM-59 > URL: http://jira.codehaus.org/browse/MRM-59 > Project: Maven Repository Manager > Type: New Feature > Components: remote proxy > Reporter: Tim Clemons > Assignee: Edwin Punzalan > Fix For: 1.0-alpha-1 > > Original Estimate: 12 hours > Remaining: 12 hours > > Have the maven-proxy act as either a maven 1.x or maven 2.x repository, > depending on which client accesses it. Brett believed this should be > managable with aliasing. > This was originally posted as a maven-proxy feature at > http://jira.codehaus.org/browse/MAVENPROXY-39 -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MRM-95) Allow cache timeout configurations for each proxied remote repository
[ http://jira.codehaus.org/browse/MRM-95?page=all ] Edwin Punzalan closed MRM-95: - Resolution: Fixed > Allow cache timeout configurations for each proxied remote repository > - > > Key: MRM-95 > URL: http://jira.codehaus.org/browse/MRM-95 > Project: Maven Repository Manager > Type: Task > Components: remote proxy > Versions: 1.0-alpha-1 > Reporter: Edwin Punzalan > Assignee: Edwin Punzalan > > Original Estimate: 12 hours >Time Spent: 6 hours > Remaining: 6 hours > -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MRM-41) discover standalone POMs
[ 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.codehaus.org/browse/MRM-41 > Project: Maven Repository Manager > Type: Task > Components: discovery > Reporter: Brett Porter > Assignee: John Tolentino > Fix For: 1.0-alpha-1 > Attachments: MRM-41-maven-repository-discovery.diff, > MRM-41-maven-repository-discovery.diff, > MRM-41-maven-repository-discovery.diff, repository-manager.diff > > Time Spent: 21 hours >Remaining: 0 minutes > > where the pom is the artifact -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-41) discover standalone POMs
[ 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://jira.codehaus.org/browse/MRM-41 > Project: Maven Repository Manager > Type: Task > Components: discovery > Reporter: Brett Porter > Assignee: John Tolentino > Fix For: 1.0-alpha-1 > Attachments: MRM-41-maven-repository-discovery.diff, > MRM-41-maven-repository-discovery.diff, > MRM-41-maven-repository-discovery.diff, repository-manager.diff > > Time Spent: 18 hours >Remaining: 0 minutes > > where the pom is the artifact -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MRM-15) partial POM written even on exception
[ 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 exception > - > > Key: MRM-15 > URL: http://jira.codehaus.org/browse/MRM-15 > Project: Maven Repository Manager > Type: Bug > Components: repository-converter > Reporter: Brett Porter > Assignee: Brett Porter > Fix For: 1.0-alpha-1 > > > I found I Was getting an CCE in the translator, and a partial pom was still > written out to disk. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MRM-15) partial POM written even on exception
[ 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 written even on exception > - > > Key: MRM-15 > URL: http://jira.codehaus.org/browse/MRM-15 > Project: Maven Repository Manager > Type: Bug > Components: repository-converter > Reporter: Brett Porter > Fix For: 1.0-alpha-1 > > > I found I Was getting an CCE in the translator, and a partial pom was still > written out to disk. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MRM-62) read maven-proxy configuration
[ 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: - localStore - browsability - remote repositories: - cacheFailures - cachePeriod - hardFail > read maven-proxy configuration > -- > > Key: MRM-62 > URL: http://jira.codehaus.org/browse/MRM-62 > Project: Maven Repository Manager > Type: Bug > Components: remote proxy > Reporter: Brett Porter > Assignee: Edwin Punzalan > Fix For: 1.0-alpha-1 > > Original Estimate: 18 hours >Time Spent: 5 hours > Remaining: 13 hours > -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-70) Browse by Group/Artifact/Version
[ 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/Version > > > Key: MRM-70 > URL: http://jira.codehaus.org/browse/MRM-70 > Project: Maven Repository Manager > Type: Task > Components: browser > Versions: 1.0-alpha-1 > Reporter: John Tolentino > Assignee: John Tolentino > > -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MRM-74) Browse web user interface
[ 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://jira.codehaus.org/browse/MRM-74 > Project: Maven Repository Manager > Type: Task > Components: web application > Versions: 1.0-alpha-1 > Reporter: John Tolentino > Assignee: nick gonzalez > Fix For: 1.0-alpha-1 > Attachments: maven-repository-webapp-MRM-74.diff > > Original Estimate: 1 day, 16 hours > Remaining: 1 day, 16 hours > -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MRM-70) Browse by Group/Artifact/Version
[ 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 > URL: http://jira.codehaus.org/browse/MRM-70 > Project: Maven Repository Manager > Type: Task > Components: browser > Versions: 1.0-alpha-1 > Reporter: John Tolentino > Assignee: John Tolentino > Fix For: 1.0-alpha-1 > > Original Estimate: 8 hours > Remaining: 8 hours > -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MRM-38) add a background task scheduler
[ 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 > URL: http://jira.codehaus.org/browse/MRM-38 > Project: Maven Repository Manager > Type: New Feature > Components: scheduling > Reporter: Brett Porter > Assignee: John Tolentino > Fix For: 1.0-alpha-1 > Attachments: MRM-38-maven-repository-webapp.diff, > maven-repository-webapp.diff > > Time Spent: 13 hours, 3 minutes >Remaining: 0 minutes > > we need to be able to schedule tasks. We should use quartz, and reuse code > from Continuum that does similarly. > There needs to be a way to add/remove/configure scheduled tasks such as > indexing, report execution and syncing -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Reopened: (MRM-38) add a background task scheduler
[ 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://jira.codehaus.org/browse/MRM-38 > Project: Maven Repository Manager > Type: New Feature > Components: scheduling > Reporter: Brett Porter > Assignee: John Tolentino > Fix For: 1.0-alpha-1 > Attachments: MRM-38-maven-repository-webapp.diff, > maven-repository-webapp.diff > > Time Spent: 13 hours, 3 minutes >Remaining: 0 minutes > > we need to be able to schedule tasks. We should use quartz, and reuse code > from Continuum that does similarly. > There needs to be a way to add/remove/configure scheduled tasks such as > indexing, report execution and syncing -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MRM-38) add a background task scheduler
[ 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 > URL: http://jira.codehaus.org/browse/MRM-38 > Project: Maven Repository Manager > Type: New Feature > Components: scheduling > Reporter: Brett Porter > Assignee: John Tolentino > Fix For: 1.0-alpha-1 > Attachments: MRM-38-maven-repository-webapp.diff, > maven-repository-webapp.diff > > Time Spent: 13 hours, 3 minutes >Remaining: 0 minutes > > we need to be able to schedule tasks. We should use quartz, and reuse code > from Continuum that does similarly. > There needs to be a way to add/remove/configure scheduled tasks such as > indexing, report execution and syncing -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MRM-14) utilise repository relocation information to update dependencies
[ 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 event to search the index for all artifacts that depends on a relocated artifact and update them as appropriate. > utilise repository relocation information to update dependencies > > > Key: MRM-14 > URL: http://jira.codehaus.org/browse/MRM-14 > Project: Maven Repository Manager > Type: New Feature > Components: repository-converter > Reporter: Brett Porter > Assignee: Edwin Punzalan > > > since repoclean loads up all the poms it can know which have been relocated > and automatically update the dependency information of some poms as they are > converted. > I think this is appropriate, but maybe the original should be retained? -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MRM-13) utilise repository relocation information during conversion of an artifact
[ http://jira.codehaus.org/browse/MRM-13?page=all ] Edwin Punzalan closed MRM-13: - Resolution: Fixed > utilise repository relocation information during conversion of an artifact > -- > > Key: MRM-13 > URL: http://jira.codehaus.org/browse/MRM-13 > Project: Maven Repository Manager > Type: New Feature > Components: repository-converter > Reporter: Brett Porter > Assignee: Edwin Punzalan > Fix For: 1.0-alpha-1 > > Original Estimate: 1 day >Time Spent: 12 hours > Remaining: 0 minutes > > we should allow some extra metdata in the m1 pom that can be recognised as > relocation information: > > > > > > > when encountering this, the converted POM and JAR will go to the new location > in the m2 repository, and the marker POM (just the relocation information) > should go to the old location (and any artifact there should be removed) > This would allow us to move Jakarta commons en mass to the dotted groupId > layout for example. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-74) Browse web user interface
[ 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 > Project: Maven Repository Manager > Type: Task > Components: web application > Versions: 1.0-alpha-1 > Reporter: John Tolentino > Assignee: nick gonzalez > Fix For: 1.0-alpha-1 > Attachments: maven-repository-webapp-MRM-74.diff > > Original Estimate: 1 day, 16 hours > Remaining: 1 day, 16 hours > -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-70) Browse by Group/Artifact/Version
[ 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.org/browse/MRM-70 > Project: Maven Repository Manager > Type: Task > Components: browser > Versions: 1.0-alpha-1 > Reporter: John Tolentino > Assignee: John Tolentino > Fix For: 1.0-alpha-1 > > Original Estimate: 8 hours > Remaining: 8 hours > -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-81) Search web user interface
[ 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 > Project: Maven Repository Manager > Type: Task > Components: web application > Versions: 1.0-alpha-1 > Reporter: John Tolentino > Fix For: 1.0-alpha-1 > > Original Estimate: 16 hours > Remaining: 16 hours > > General search page and search result page. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MRM-79) Repository Interface web user interface
[ 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 > URL: http://jira.codehaus.org/browse/MRM-79 > Project: Maven Repository Manager > Type: Task > Components: web application > Versions: 1.0-alpha-1 > Reporter: John Tolentino > > Original Estimate: 4 hours > Remaining: 4 hours > > Manual removal of lockfile can be done here. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-14) utilise repository relocation information to update dependencies
[ 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 dependencies > > > Key: MRM-14 > URL: http://jira.codehaus.org/browse/MRM-14 > Project: Maven Repository Manager > Type: New Feature > Components: repository-converter > Reporter: Brett Porter > > > since repoclean loads up all the poms it can know which have been relocated > and automatically update the dependency information of some poms as they are > converted. > I think this is appropriate, but maybe the original should be retained? -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-11) Security policy for uploads must be in place
[ 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 > URL: http://jira.codehaus.org/browse/MRM-11 > Project: Maven Repository Manager > Type: Task > Components: design > Reporter: Jason van Zyl > > -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-28) sync shouldn't use file sizes as basis - updated checksums are not resynced
[ 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 resynced > --- > > Key: MRM-28 > URL: http://jira.codehaus.org/browse/MRM-28 > Project: Maven Repository Manager > Type: Bug > Components: partner sync > Reporter: Brett Porter > > > currently the sync from a partner repo does not reget checksums that have > changed, so if they are created mistakenly they are not updated. > That said, we should be warned of an occurrence where such a file changes. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-12) POI directory structure incorrectly converted from m1 repo
[ 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 > -- > > Key: MRM-12 > URL: http://jira.codehaus.org/browse/MRM-12 > Project: Maven Repository Manager > Type: Bug > Components: repository-converter > Reporter: Carlos Sanchez > > > The POI files are in directories like > http://www.ibiblio.org/maven2/poi/poi-2.5.1-final/20040804/ > although the pom in m1 repo and the one in the m2 have a correct version tag > "2.5.1-final-20040804" -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-10) syncopate needs to validate the incoming directory layout
[ 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 > - > > Key: MRM-10 > URL: http://jira.codehaus.org/browse/MRM-10 > Project: Maven Repository Manager > Type: Improvement > Components: partner sync > Reporter: Brett Porter > > > we need to validate a couple of things: > 1) that the incoming content from sources is in the correct layout, and error > on stuff that isn't. dist.codehaus.org are often offenders here (eg > http://www.ibiblio.org/maven/non-codehaus/) > 2) we should probably restrict the group IDs synced, to prevent - for example > - codehaus uploading Apache artifacts over the official ones -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-90) add advanced search options
[ 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.org/browse/MRM-90 > Project: Maven Repository Manager > Type: New Feature > Components: web application > Reporter: Brett Porter > > > we need to add the ability to query on particular fields and across some > ranges. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MRM-58) create a search result class for returning from search
[ 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 search > -- > > Key: MRM-58 > URL: http://jira.codehaus.org/browse/MRM-58 > Project: Maven Repository Manager > Type: Bug > Components: indexing > Reporter: Brett Porter > Assignee: Maria Odea Ching > Fix For: 1.0-alpha-1 > > Original Estimate: 6 hours >Time Spent: 5 hours > Remaining: 1 hour > > instead of returning artifacts, return a search result class including > artifact, classes, packages and 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MRM-57) ability to retrieve matched portion of classes, packages and files fields
[ 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 fields > - > > Key: MRM-57 > URL: http://jira.codehaus.org/browse/MRM-57 > Project: Maven Repository Manager > Type: Bug > Components: indexing > Reporter: Brett Porter > Assignee: Maria Odea Ching > Fix For: 1.0-alpha-1 > Attachments: MRM-57-maven-repository-indexer.patch, > MRM-57-maven-repository-indexing.patch > > Time Spent: 21 hours >Remaining: 0 minutes > > If searching by "org.apache", it would be good to just obtain the portions of > the field that matched. This might require indexing one record per class. > Need to investigate some more, and determine whether we are using that or can > do something else. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-69) Simple "query everything" search
[ 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.codehaus.org/browse/MRM-69 > Project: Maven Repository Manager > Type: Task > Reporter: Maria Odea Ching > Assignee: Maria Odea Ching > Fix For: 1.0-alpha-1 > Attachments: MRM-69-maven-repository-indexer.patch, > MRM-69-maven-repository-indexer.patch, MRM-69-maven-repository-indexer.patch > > Original Estimate: 15 hours >Time Spent: 13 hours > Remaining: 2 hours > > Search keyword/term in any of the fields in the index. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-88) search by filename
[ 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 > Project: Maven Repository Manager > Type: Sub-task > Reporter: Maria Odea Ching > Assignee: Maria Odea Ching > Fix For: 1.0-alpha-1 > > Original Estimate: 2 hours > Remaining: 2 hours > -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-68) Accomodate "query everything" in the index
[ 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-68 > URL: http://jira.codehaus.org/browse/MRM-68 > Project: Maven Repository Manager > Type: Task > Reporter: Maria Odea Ching > Assignee: Maria Odea Ching > Fix For: 1.0-alpha-1 > > Original Estimate: 20 hours >Time Spent: 17 hours, 30 minutes > Remaining: 2 hours, 30 minutes > > Index must accomodate google-like search wherein the keyword or term can be > searched on all the fields in the index. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-97) Allow hard-fail configuration for a remote repository
[ 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 > URL: http://jira.codehaus.org/browse/MRM-97 > Project: Maven Repository Manager > Type: Task > Components: remote proxy > Versions: 1.0-alpha-1 > Reporter: Edwin Punzalan > Assignee: Edwin Punzalan > Fix For: 1.0-alpha-1 > > Original Estimate: 8 hours >Time Spent: 1 hour > Remaining: 0 minutes > > see maven-proxy configuration > http://cvs.maven-proxy.codehaus.org/maven-proxy/core/src/test/resources/org/apache/maven/proxy/config/PropertyLoaderTest1.properties?rev=1.1&view=markup -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-54) allow nested search parameters
[ 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.org/browse/MRM-54 > Project: Maven Repository Manager > Type: Task > Components: indexing > Reporter: Edwin Punzalan > Assignee: Edwin Punzalan > Fix For: 1.0-alpha-1 > > Original Estimate: 8 hours >Time Spent: 6 hours > Remaining: 0 minutes > > Search parameters should be nested to allow searches like >( ( groupId=1 AND artifactId=2 ) AND ( version=1 OR version=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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-96) Enable the use of http proxies when mrm is restricted to browse directly over the net
[ 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 > the net > - > > Key: MRM-96 > URL: http://jira.codehaus.org/browse/MRM-96 > Project: Maven Repository Manager > Type: Task > Components: remote proxy > Versions: 1.0-alpha-1 > Reporter: Edwin Punzalan > Assignee: Edwin Punzalan > Fix For: 1.0-alpha-1 > > Original Estimate: 8 hours >Time Spent: 3 hours > Remaining: 0 minutes > -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
