[jira] Updated: (MRM-594) add some minimal hook in LegacyPathParser to allow exception management in artifact resolution
[
http://jira.codehaus.org/browse/MRM-594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maria Odea Ching updated MRM-594:
-
Fix Version/s: (was: 1.1)
1.0.1
add some minimal hook in LegacyPathParser to allow exception management in
artifact resolution
--
Key: MRM-594
URL: http://jira.codehaus.org/browse/MRM-594
Project: Archiva
Issue Type: Improvement
Components: repository interface
Affects Versions: 1.0-beta-4
Reporter: nicolas de loof
Fix For: 1.0.1
Attachments: MRM-594-with-web-ui.patch, MRM-594.patch
Some existing artifacts are not available to maven1. jaxen-1.0-FCS-full for
example (use by some core maven1 plugins) can only be obtained by specifying
a classifier full.
The maven1 request /jaxen/jars/jaxen-1.0-FCS-full.jar is converted as
artifact [ jaxen : jaxen : 1.0-FCS-full ], that doesn't exist.
The LegacyPathParser is allready very complex and works for many artifact,
but cannot handle classifiers as they can be any string.
A solution to help archiva managers should be to use an resolution exception
list :
if ( exceptions.contains( path ) )
{
String exception = exceptions.getProperty( path );
String[] ref = exception.split( : );
artifact.setGroupId( ref[0] );
artifact.setArtifactId( ref[1] );
artifact.setVersion( ref[2] );
if ( ref.length 3 )
{
artifact.setClassifier( ref[3] );
}
return artifact;
}
based on a simple properties file :
jaxen/jars/jaxen-1.0-FCS-full.jar = jaxen:jaxen:1.0-FCS:full
This would allow admins to quickly fix such issues and not require archiva to
find a way to make legacy path deterministic.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MRM-594) add some minimal hook in LegacyPathParser to allow exception management in artifact resolution
[
http://jira.codehaus.org/browse/MRM-594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nicolas de loof updated MRM-594:
Attachment: MRM-594-with-web-ui.patch
This new patch covers :
- make PathParsers plexus component instead of static utility classes
- inject ArchivaConfiguration in LegacyPathParser
- extend ArchivaConfiguration to support LegacyArtifactPaths
- default archiva configuration includes support for jaxen-1.0-FCS-full
- new legacy support entry in admin web UI
- new admin action to list / add / delete LegacyArtifactPaths
- testCases updates
Please note : there may be conflicts with my patches for MRM-595 MRM 596, in
particular for testcases.
add some minimal hook in LegacyPathParser to allow exception management in
artifact resolution
--
Key: MRM-594
URL: http://jira.codehaus.org/browse/MRM-594
Project: Archiva
Issue Type: Improvement
Components: repository interface
Affects Versions: 1.0-beta-4
Reporter: nicolas de loof
Fix For: 1.1
Attachments: MRM-594-with-web-ui.patch, MRM-594.patch
Some existing artifacts are not available to maven1. jaxen-1.0-FCS-full for
example (use by some core maven1 plugins) can only be obtained by specifying
a classifier full.
The maven1 request /jaxen/jars/jaxen-1.0-FCS-full.jar is converted as
artifact [ jaxen : jaxen : 1.0-FCS-full ], that doesn't exist.
The LegacyPathParser is allready very complex and works for many artifact,
but cannot handle classifiers as they can be any string.
A solution to help archiva managers should be to use an resolution exception
list :
if ( exceptions.contains( path ) )
{
String exception = exceptions.getProperty( path );
String[] ref = exception.split( : );
artifact.setGroupId( ref[0] );
artifact.setArtifactId( ref[1] );
artifact.setVersion( ref[2] );
if ( ref.length 3 )
{
artifact.setClassifier( ref[3] );
}
return artifact;
}
based on a simple properties file :
jaxen/jars/jaxen-1.0-FCS-full.jar = jaxen:jaxen:1.0-FCS:full
This would allow admins to quickly fix such issues and not require archiva to
find a way to make legacy path deterministic.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MRM-594) add some minimal hook in LegacyPathParser to allow exception management in artifact resolution
[
http://jira.codehaus.org/browse/MRM-594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nicolas de loof updated MRM-594:
Attachment: MRM-594.patch
This patch doesn't fully solve the issue but creates the required basis for :
- converts the PathParsers to plexus components (not static utils classes), so
that it can access other components in future (archivaConfiguration ?).
- add support for custom artifacts resolution in LegacyPathParser, based on a
String representation groupId:artifactId:version:classifier:type (classifier
beeing optional)
- register a default exception to support jaxen-1.0-FCS-full (because it is
used by maven 1 itself) as demonstration of the reslution exception
- testcase
this patch must be applied on archiva-repository-layer
add some minimal hook in LegacyPathParser to allow exception management in
artifact resolution
--
Key: MRM-594
URL: http://jira.codehaus.org/browse/MRM-594
Project: Archiva
Issue Type: Improvement
Components: repository interface
Affects Versions: 1.0-beta-4
Reporter: nicolas de loof
Attachments: MRM-594.patch
Some existing artifacts are not available to maven1. jaxen-1.0-FCS-full for
example (use by some core maven1 plugins) can only be obtained by specifying
a classifier full.
The maven1 request /jaxen/jars/jaxen-1.0-FCS-full.jar is converted as
artifact [ jaxen : jaxen : 1.0-FCS-full ], that doesn't exist.
The LegacyPathParser is allready very complex and works for many artifact,
but cannot handle classifiers as they can be any string.
A solution to help archiva managers should be to use an resolution exception
list :
if ( exceptions.contains( path ) )
{
String exception = exceptions.getProperty( path );
String[] ref = exception.split( : );
artifact.setGroupId( ref[0] );
artifact.setArtifactId( ref[1] );
artifact.setVersion( ref[2] );
if ( ref.length 3 )
{
artifact.setClassifier( ref[3] );
}
return artifact;
}
based on a simple properties file :
jaxen/jars/jaxen-1.0-FCS-full.jar = jaxen:jaxen:1.0-FCS:full
This would allow admins to quickly fix such issues and not require archiva to
find a way to make legacy path deterministic.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MRM-594) add some minimal hook in LegacyPathParser to allow exception management in artifact resolution
[
http://jira.codehaus.org/browse/MRM-594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter updated MRM-594:
-
Fix Version/s: 1.1
do you mind if we hold this for post 1.0, since it's a feature? I don't want to
risk any late breaking regressions :)
add some minimal hook in LegacyPathParser to allow exception management in
artifact resolution
--
Key: MRM-594
URL: http://jira.codehaus.org/browse/MRM-594
Project: Archiva
Issue Type: Improvement
Components: repository interface
Affects Versions: 1.0-beta-4
Reporter: nicolas de loof
Fix For: 1.1
Attachments: MRM-594.patch
Some existing artifacts are not available to maven1. jaxen-1.0-FCS-full for
example (use by some core maven1 plugins) can only be obtained by specifying
a classifier full.
The maven1 request /jaxen/jars/jaxen-1.0-FCS-full.jar is converted as
artifact [ jaxen : jaxen : 1.0-FCS-full ], that doesn't exist.
The LegacyPathParser is allready very complex and works for many artifact,
but cannot handle classifiers as they can be any string.
A solution to help archiva managers should be to use an resolution exception
list :
if ( exceptions.contains( path ) )
{
String exception = exceptions.getProperty( path );
String[] ref = exception.split( : );
artifact.setGroupId( ref[0] );
artifact.setArtifactId( ref[1] );
artifact.setVersion( ref[2] );
if ( ref.length 3 )
{
artifact.setClassifier( ref[3] );
}
return artifact;
}
based on a simple properties file :
jaxen/jars/jaxen-1.0-FCS-full.jar = jaxen:jaxen:1.0-FCS:full
This would allow admins to quickly fix such issues and not require archiva to
find a way to make legacy path deterministic.
--
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
