Description of problem:
gradle package is currently using plexus-container-default. Please migrate to a newer container, such as plexus-containers-container-default or sisu-inject-plexus.
Currently gradle is the only package that requires or build-requires plexus-container-default. plexus-container-default is unmaintained upstream for several years and two other packages provide mostly compatible API. Because of that plexus-container-default will be retired and gradle should migrate to more recent container to keep working.
Version-Release number of selected component (if applicable):
for now I do not it is possible, given that the current existing version requires
plexus-container-default and maven 2.x.
i have to enable a plugin (gradle maven plugin) if I want to import the latest release of gradle, and then remove the dependency in question
I've tried to use the most recent versions of container-default, but then gradle does not work. cause: incompatible apis
(In reply to comment #2)
> I've tried to use the most recent versions of container-default, but then
> gradle does not work. cause: incompatible apis
The incompatibilities are minor and usually easy to overcome.
The right solution is working with upstream to move to newer container API, preferably providing patches. I have done that myself for some packages I maintain (for eg. ), upstreams are usually happy to accept patches.
Created attachment 778067 [details]
Can you try the patch Mikolaj provided?
Is there something that works if the patch is not applied but breaks if applied?
If yes please give instructions how to test it.
unfortunately the patch is not applicable, make it unusable gradle
Could you provide more details?
Gradle builds with this patch and it is able to rebuild itself.
Could you explain what errors you get with the patch applied?
error: cannot find symbol
symbol: method addJarResource(File)
location: variable plexusContainer of type PlexusContainer
the patch provided is incomplete,
must be changed also references in subprojects/core-impl/core-impl.gradle
(see PATCH24) and ant build script
also for the latest release 1.6 the problem persist, this is a maven-ant-task inherits ...
As far as I know maven-ant-tasks is broken in Fedora as it Requires Maven 2 and doesn't work with Maven 3.
For Maven 3 you should use aether-ant-tasks instead.
(In reply to Mikolaj Izdebski from comment #11)
> As far as I know maven-ant-tasks is broken in Fedora as it Requires Maven 2
> and doesn't work with Maven 3.
> For Maven 3 you should use aether-ant-tasks instead.
sorry but isnt compatible
(In reply to gil cattaneo from comment #12)
> (In reply to Mikolaj Izdebski from comment #11)
> > As far as I know maven-ant-tasks is broken in Fedora as it Requires Maven 2
> > and doesn't work with Maven 3.
> > For Maven 3 you should use aether-ant-tasks instead.
> sorry but isnt compatible
It is mostly compatible, with some small exceptions.
if you have to apply a patch to make it compatible with aether ant task is welcome
Gil, you have reported the incompatibility yourself to the upstream, 10 months ago . There was no response from maintainers. Clearly it's legacy software which shouldn't be used.
Aether Ant tasks are actively maintained. There is quite recent activity in their git repository. Maintainers usually respond on mailing lists within one day.
IMHO instead of insisting on keeping old software you should try to update to newer upstream versions and, if needed, convince upstreams to do the same, providing patches if needed.
Created attachment 778727 [details]
Created attachment 778728 [details]
I was able to bootstrap gradle against the newer plexus-containers-container-default package by using the two patches I've just attached.
Do you have a use case that illustrates the maven-ant-tasks problem? If I can get a reproducable problem case, I can work on fixing it (probably by using aether-ant-tasks instead, as Mikolaj suggests.)
try with http://gil.fedorapeople.org/gradle/gradle-1.6-1.fc19.src.rpm
in boostrap mode (already set) and disable in ant build script only the references on M-A-T.
Thanks gil, I am looking at this now.
This bug appears to have been reported against 'rawhide' during the Fedora 20 development cycle.
Changing version to '20'.
More information and reason for this action is here:
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.