[jira] [Created] (MINDEXER-102) Forward port OSGI related index-reader changes to master (Changes relative to MINDEXER-100 branch)
Simon Spero created MINDEXER-102: Summary: Forward port OSGI related index-reader changes to master (Changes relative to MINDEXER-100 branch) Key: MINDEXER-102 URL: https://issues.apache.org/jira/browse/MINDEXER-102 Project: Maven Indexer Issue Type: Task Affects Versions: 6.0 Reporter: Simon Spero Fix For: 6.0 Forward port the OSGI related changes to index-reader from MINDEXER-97 . Changes must be made relative to MINDEXER-100 branch -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (MINDEXER-101) Forward port OSGI improvements (MINDEXER-97) to master
Simon Spero created MINDEXER-101: Summary: Forward port OSGI improvements (MINDEXER-97) to master Key: MINDEXER-101 URL: https://issues.apache.org/jira/browse/MINDEXER-101 Project: Maven Indexer Issue Type: Task Reporter: Simon Spero -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MINDEXER-100) Forward port changes in 5.1.2-SNAPSHOT (maven-indexer-5.x) to 6.0.0-SNAPSHOT (master)
[ https://issues.apache.org/jira/browse/MINDEXER-100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15931980#comment-15931980 ] Simon Spero commented on MINDEXER-100: -- Will forward port MINDEXER-97 changes if both sets merged, > Forward port changes in 5.1.2-SNAPSHOT (maven-indexer-5.x) to 6.0.0-SNAPSHOT > (master) > - > > Key: MINDEXER-100 > URL: https://issues.apache.org/jira/browse/MINDEXER-100 > Project: Maven Indexer > Issue Type: Task >Affects Versions: 6.0 >Reporter: Simon Spero > Fix For: 6.0 > > > The master branch and the 5.x branch have diverged, with new components like > the index-reader module not included in master. > > I have submitted github pull requests against the 5.x (MINDEXER-97) which > should also be included in master. > Commits 5.x made since the divergence from master should be reviewed, and > forward ported to master if still relevant -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (MINDEXER-100) Forward port changes in 5.1.2-SNAPSHOT (maven-indexer-5.x) to 6.0.0-SNAPSHOT (master)
[ https://issues.apache.org/jira/browse/MINDEXER-100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Spero updated MINDEXER-100: - Affects Version/s: (was: 5.1.2) > Forward port changes in 5.1.2-SNAPSHOT (maven-indexer-5.x) to 6.0.0-SNAPSHOT > (master) > - > > Key: MINDEXER-100 > URL: https://issues.apache.org/jira/browse/MINDEXER-100 > Project: Maven Indexer > Issue Type: Task >Affects Versions: 6.0 >Reporter: Simon Spero > Fix For: 6.0 > > > The master branch and the 5.x branch have diverged, with new components like > the index-reader module not included in master. > > I have submitted github pull requests against the 5.x (MINDEXER-97) which > should also be included in master. > Commits 5.x made since the divergence from master should be reviewed, and > forward ported to master if still relevant -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MINDEXER-100) Forward port changes in 5.1.2-SNAPSHOT (maven-indexer-5.x) to 6.0.0-SNAPSHOT (master)
[
https://issues.apache.org/jira/browse/MINDEXER-100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15931903#comment-15931903
]
Simon Spero commented on MINDEXER-100:
--
The following commits are in 5.x, but are not in master.
{code:title=git log --reverse upstream/master..upstream/maven-indexer-5.x}
commit 7a0e7ad3d92fc121c2c1e49414d2c1099d945db4
Author: Tamas Cservenak
Date: Sat Oct 31 00:10:13 2015 +0100
MINDEXER-94: Temp file cleanup on errors
commit 0f1724507b9035d0dd855d2a4f8e2f75c01db277
Author: Tamas Cservenak
Date: Sat Oct 31 01:05:08 2015 +0100
Add Idea iml files to rat exclude
commit c193888287ca04a7e6038dddf596b13124769180
Author: Tamas Cservenak
Date: Sat Oct 31 01:15:45 2015 +0100
MINDEXER-95: Suboptimal indexing execution in updater
commit af8783d8fc8dcab6ef6d9a17d04858fd725037a0
Author: Tamas Cservenak
Date: Sat Oct 31 01:29:30 2015 +0100
MINDEXER-96: Indexer reader
commit b9c4d90810b6174a1851c179ffebf2c3456c4c66
Author: Tamas Cservenak
Date: Tue Nov 3 12:28:41 2015 +0100
Added index writer, that writes single chunk for now
commit 5c75bbac75a420ed19327c4300eaa6cfbbd771ad
Author: Tamas Cservenak
Date: Tue Nov 3 14:23:32 2015 +0100
MINDEXER-96: Indexer reader and writer
commit be227e284d81507d3f67e54d39e63af55a6feb24
Author: Tamas Cservenak
Date: Tue Nov 3 16:38:26 2015 +0100
INDEXER-96: Fix iterators
commit c3431b6e84c39a2e4f56fe33e888702f826c701c
Author: Tamas Cservenak
Date: Thu Nov 5 10:53:26 2015 +0100
Cleanup
commit 4c5d1d61e9691473053551dee7645ebf0873bb26
Author: Tamas Cservenak
Date: Thu Nov 5 13:53:34 2015 +0100
Make the reader an osgi bundle
commit 4333789f769e3441ba133207294aae4d3f6a2eb9
Author: Tamas Cservenak
Date: Thu Nov 5 15:36:13 2015 +0100
rename helper class to avoid name clash with other utilities
commit ea1205e85f3325263b5319fe6ae9e255733084d0
Author: Tamas Cservenak
Date: Wed Nov 11 21:11:06 2015 +0100
Fix classifier separator
commit e0570bff5c60604115ab7ad0d5498055a60fc772
Author: Tamas Cservenak
Date: Thu Nov 12 11:30:50 2015 +0100
Remove Transform, let user use any lib it wants to for iterable manipulation
Also, UTs got new TestUtils based on Guava
{code}
> Forward port changes in 5.1.2-SNAPSHOT (maven-indexer-5.x) to 6.0.0-SNAPSHOT
> (master)
> -
>
> Key: MINDEXER-100
> URL: https://issues.apache.org/jira/browse/MINDEXER-100
> Project: Maven Indexer
> Issue Type: Task
>Affects Versions: 5.1.2, 6.0
>Reporter: Simon Spero
> Fix For: 6.0
>
>
> The master branch and the 5.x branch have diverged, with new components like
> the index-reader module not included in master.
>
> I have submitted github pull requests against the 5.x (MINDEXER-97) which
> should also be included in master.
> Commits 5.x made since the divergence from master should be reviewed, and
> forward ported to master if still relevant
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (MINDEXER-100) Forward port changes in 5.1.2-SNAPSHOT (maven-indexer-5.x) to 6.0.0-SNAPSHOT (master)
Simon Spero created MINDEXER-100: Summary: Forward port changes in 5.1.2-SNAPSHOT (maven-indexer-5.x) to 6.0.0-SNAPSHOT (master) Key: MINDEXER-100 URL: https://issues.apache.org/jira/browse/MINDEXER-100 Project: Maven Indexer Issue Type: Task Affects Versions: 5.1.2, 6.0 Reporter: Simon Spero Fix For: 6.0 The master branch and the 5.x branch have diverged, with new components like the index-reader module not included in master. I have submitted github pull requests against the 5.x (MINDEXER-97) which should also be included in master. Commits 5.x made since the divergence from master should be reviewed, and forward ported to master if still relevant -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MINDEXER-97) Add OSGi 5.0 MANIFEST headers to OsgiArtifactIndexCreator
[ https://issues.apache.org/jira/browse/MINDEXER-97?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15928062#comment-15928062 ] Simon Spero commented on MINDEXER-97: - An important addition to the manifest headers is the artifact SHA-256, which is required for content. Since full SHA-1 has now fallen, this wouldn't be of value only to OSGI. Furthermore, the deprecated Export-Service header is indexed (though Import-Service isn't). Both these headers were never used by any resolvers, which is why they could be deprecated. I can make these changes and submit a pull request from github. I'm not sure if I can make it track this issue. When is the next release scheduled, and would a changed version be likely to be used on maven central relatively soon thereafter? > Add OSGi 5.0 MANIFEST headers to OsgiArtifactIndexCreator > - > > Key: MINDEXER-97 > URL: https://issues.apache.org/jira/browse/MINDEXER-97 > Project: Maven Indexer > Issue Type: Improvement >Reporter: Balazs Zsoldos > > It would be extremely useful if the following MANIFEST headers were added to > the index: > - Require-Capability > - Provide-Capability > - DynamicImport-Package > Especially the first two would be necessary to be able to build up a database > that helps finding dependencies for unsatisfied bundles. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (MRESOLVER-17) Re-parent maven-resolver-provider to maven-resolver (github pull request #3)
Simon Spero created MRESOLVER-17: Summary: Re-parent maven-resolver-provider to maven-resolver (github pull request #3) Key: MRESOLVER-17 URL: https://issues.apache.org/jira/browse/MRESOLVER-17 Project: Maven Resolver Issue Type: Improvement Components: resolver Reporter: Simon Spero Priority: Minor [This project doesn't seem to be set up to auto-create issues for pull requests in JIRA] See https://github.com/apache/maven-resolver/pull/3 History is preserved, hence the seemingly large number of commits. The actual new commits are at the end, and are changes to the poms, plus a couple of minimal doc comments to avoid checkstyle fail. The changes to the poms mostly involve version bumps to try and get as many plexus versions as possible to line up (provider was failing to find classes.) Wagon was bumped to latest release. The version of the maven dependencies is configurable ; the pull request uses 3.3.9. - PR comment: The changes make maven-resolver-provider a sub-project of maven-resolver, instead of the main maven repository. These changes allow maven-resolver-provider to be built against maven-3.3.9. This might make it easier to create a release version of the entire maven-resolver-suite, with version numbers in the maven-resolver sequence, rather than the maven line. Fortunately, the missing OSGI metadata in the jar manifests makes the drop in version numbers less problematic. It would be nice to have these jars be bundles again, since aether is used for provisioning OSGI bundles by containers like Apache Karaf. Plexus versions are not quite all lined up, but the provider provides (which is more than it did before the version bumping). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
