You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@stanbol.apache.org by Reto Bachmann-Gmür <re...@apache.org> on 2013/02/01 00:37:00 UTC
Re: STANBOL-888 and bundle-lists
Ok, the launcher was depending on an old SNAPSHOT version of the contenthub
bundlelist.
We really should find a way to ensure that when an artifact is released no
other project still depends on the old snapshot version.
Cheers,
Reto
On Thu, Jan 31, 2013 at 11:56 PM, Reto Bachmann-Gmür <re...@apache.org>wrote:
> I'm geting the following error:
>
> [ERROR] Failed to execute goal
> org.apache.sling:maven-launchpad-plugin:2.2.0:prepare-package
> (prepare-package) on project org.apache.stanbol.launchers.full: Unable to
> find artifact. Could not find artifact
> org.apache.stanbol:org.apache.stanbol.contenthub.servicesapi:jar:0.10.0-SNAPSHOT
> in apache.snapshots (http://repository.apache.org/snapshots)
>
> It seems that there's still a reference to this old snapshot version
> somewehere but I can't find it....
>
> Any idea?
>
> Cheers,
> Reto
>
>
> On Thu, Jan 31, 2013 at 5:32 PM, Reto Bachmann-Gmür <re...@wymiwyg.com>wrote:
>
>> Hi
>>
>> Thanks for spotting this qualifier. Indeed I've seen the error in fact it
>> seems to be the one reported here against the fusepool platform:
>>
>> https://github.com/fusepool/fusepool-platform/issues/3
>>
>> curiosly enough for me the error did not appear when compiling stanbol by
>> itself but only when compiling an outer reactor conting stanbol an also
>> only if this reactor contained another project using the
>> sling-launchpad-plugin.
>>
>> Could you commit your code using version 2.2.0 of the plugin?
>>
>> Cheers,
>> Reto
>>
>>
>> On Thu, Jan 31, 2013 at 4:49 PM, Rupert Westenthaler <
>> rupert.westenthaler@gmail.com> wrote:
>>
>>> Hi
>>>
>>> while working on the bundle lists I encountered an other issue that
>>> suddenly appeared
>>>
>>> The pom of org.apache.stanbol.commons.security.usermanagement:0.11.0"
>>> [1] contains the following dependency
>>>
>>> <dependency>
>>> <groupId>org.apache.stanbol</groupId>
>>> <artifactId>org.apache.stanbol.commons.security.core</artifactId>
>>> <version>0.11.0</version>
>>> <type>bundle</type>
>>> </dependency>
>>>
>>> Note the '<type>bundle<type>'
>>>
>>> Thus caused maven to request
>>>
>>>
>>> http://repo.maven.apache.org/maven2/org/apache/stanbol/org.apache.stanbol.commons.security.core/0.11.0/org.apache.stanbol.commons.security.core-0.11.0.bundle
>>>
>>> a file that does not exist. Because of that I was getting the following
>>>
>>> Failed to execute goal on project
>>> org.apache.stanbol.launchers.bundlelists.security: Could not resolve
>>> dependencies for project
>>>
>>> org.apache.stanbol:org.apache.stanbol.launchers.bundlelists.security:partialbundlelist:0.10.0-SNAPSHOT:
>>> Could not find artifact
>>> org.apache.stanbol:org.apache.stanbol.commons.security.core:bundle:0.11.0
>>> in central (http://repo.maven.apache.org/maven2) -> [Help 1]
>>>
>>> Removing '<type>bundle</type>' in the 0.12.0-SNAPSHOT version solved
>>> the issue for me. If this can be validated by other it might mean that
>>> we need to release a 0.11.1 version of this module that fixes this
>>> before releasing the bundlelists and launchers.
>>>
>>> Can someone please try to replicate that by changing the versions of
>>> all Stanbol modules referenced by the security bundlelist to '0.11.0'
>>>
>>>
>>> BTW:
>>>
>>> On Thu, Jan 31, 2013 at 2:22 PM, Reto Bachmann-Gmür <re...@apache.org>
>>> wrote:
>>> > My guess is that this has to do with
>>> > different versions of the maven-launchpad-plugin being used. Is there a
>>> > reason for not using the latest version (2.2.0) in stanbol?
>>> >
>>>
>>> My local version is already using version 2.2.0.
>>>
>>> best
>>> Rupert
>>>
>>> [1]
>>> http://search.maven.org/remotecontent?filepath=org/apache/stanbol/org.apache.stanbol.commons.security.usermanagement/0.11.0/org.apache.stanbol.commons.security.usermanagement-0.11.0.pom
>>>
>>>
>>> --
>>> | Rupert Westenthaler rupert.westenthaler@gmail.com
>>> | Bodenlehenstraße 11 ++43-699-11108907
>>> | A-5500 Bischofshofen
>>>
>>
>>
>
Re: STANBOL-888 and bundle-lists
Posted by Rupert Westenthaler <ru...@gmail.com>.
Hi
I have not yet committed those changes. However I think I can complete
those work today before noun.
best
Rupert
On Fri, Feb 1, 2013 at 12:37 AM, Reto Bachmann-Gmür <re...@apache.org> wrote:
> Ok, the launcher was depending on an old SNAPSHOT version of the contenthub
> bundlelist.
>
> We really should find a way to ensure that when an artifact is released no
> other project still depends on the old snapshot version.
>
> Cheers,
> Reto
>
> On Thu, Jan 31, 2013 at 11:56 PM, Reto Bachmann-Gmür <re...@apache.org>wrote:
>
>> I'm geting the following error:
>>
>> [ERROR] Failed to execute goal
>> org.apache.sling:maven-launchpad-plugin:2.2.0:prepare-package
>> (prepare-package) on project org.apache.stanbol.launchers.full: Unable to
>> find artifact. Could not find artifact
>> org.apache.stanbol:org.apache.stanbol.contenthub.servicesapi:jar:0.10.0-SNAPSHOT
>> in apache.snapshots (http://repository.apache.org/snapshots)
>>
>> It seems that there's still a reference to this old snapshot version
>> somewehere but I can't find it....
>>
>> Any idea?
>>
>> Cheers,
>> Reto
>>
>>
>> On Thu, Jan 31, 2013 at 5:32 PM, Reto Bachmann-Gmür <re...@wymiwyg.com>wrote:
>>
>>> Hi
>>>
>>> Thanks for spotting this qualifier. Indeed I've seen the error in fact it
>>> seems to be the one reported here against the fusepool platform:
>>>
>>> https://github.com/fusepool/fusepool-platform/issues/3
>>>
>>> curiosly enough for me the error did not appear when compiling stanbol by
>>> itself but only when compiling an outer reactor conting stanbol an also
>>> only if this reactor contained another project using the
>>> sling-launchpad-plugin.
>>>
>>> Could you commit your code using version 2.2.0 of the plugin?
>>>
>>> Cheers,
>>> Reto
>>>
>>>
>>> On Thu, Jan 31, 2013 at 4:49 PM, Rupert Westenthaler <
>>> rupert.westenthaler@gmail.com> wrote:
>>>
>>>> Hi
>>>>
>>>> while working on the bundle lists I encountered an other issue that
>>>> suddenly appeared
>>>>
>>>> The pom of org.apache.stanbol.commons.security.usermanagement:0.11.0"
>>>> [1] contains the following dependency
>>>>
>>>> <dependency>
>>>> <groupId>org.apache.stanbol</groupId>
>>>> <artifactId>org.apache.stanbol.commons.security.core</artifactId>
>>>> <version>0.11.0</version>
>>>> <type>bundle</type>
>>>> </dependency>
>>>>
>>>> Note the '<type>bundle<type>'
>>>>
>>>> Thus caused maven to request
>>>>
>>>>
>>>> http://repo.maven.apache.org/maven2/org/apache/stanbol/org.apache.stanbol.commons.security.core/0.11.0/org.apache.stanbol.commons.security.core-0.11.0.bundle
>>>>
>>>> a file that does not exist. Because of that I was getting the following
>>>>
>>>> Failed to execute goal on project
>>>> org.apache.stanbol.launchers.bundlelists.security: Could not resolve
>>>> dependencies for project
>>>>
>>>> org.apache.stanbol:org.apache.stanbol.launchers.bundlelists.security:partialbundlelist:0.10.0-SNAPSHOT:
>>>> Could not find artifact
>>>> org.apache.stanbol:org.apache.stanbol.commons.security.core:bundle:0.11.0
>>>> in central (http://repo.maven.apache.org/maven2) -> [Help 1]
>>>>
>>>> Removing '<type>bundle</type>' in the 0.12.0-SNAPSHOT version solved
>>>> the issue for me. If this can be validated by other it might mean that
>>>> we need to release a 0.11.1 version of this module that fixes this
>>>> before releasing the bundlelists and launchers.
>>>>
>>>> Can someone please try to replicate that by changing the versions of
>>>> all Stanbol modules referenced by the security bundlelist to '0.11.0'
>>>>
>>>>
>>>> BTW:
>>>>
>>>> On Thu, Jan 31, 2013 at 2:22 PM, Reto Bachmann-Gmür <re...@apache.org>
>>>> wrote:
>>>> > My guess is that this has to do with
>>>> > different versions of the maven-launchpad-plugin being used. Is there a
>>>> > reason for not using the latest version (2.2.0) in stanbol?
>>>> >
>>>>
>>>> My local version is already using version 2.2.0.
>>>>
>>>> best
>>>> Rupert
>>>>
>>>> [1]
>>>> http://search.maven.org/remotecontent?filepath=org/apache/stanbol/org.apache.stanbol.commons.security.usermanagement/0.11.0/org.apache.stanbol.commons.security.usermanagement-0.11.0.pom
>>>>
>>>>
>>>> --
>>>> | Rupert Westenthaler rupert.westenthaler@gmail.com
>>>> | Bodenlehenstraße 11 ++43-699-11108907
>>>> | A-5500 Bischofshofen
>>>>
>>>
>>>
>>
--
| Rupert Westenthaler rupert.westenthaler@gmail.com
| Bodenlehenstraße 11 ++43-699-11108907
| A-5500 Bischofshofen
Re: STANBOL-888 and bundle-lists
Posted by Fabian Christ <ch...@googlemail.com>.
2013/2/1 Reto Bachmann-Gmür <re...@apache.org>:
> We really should find a way to ensure that when an artifact is released no
> other project still depends on the old snapshot version.
Yes - this is really a pain.
I have tried many combinations of goal with the Maven versions plugin
but it seems to be a bit buggy. At least, I had the situation where
some artifacts were updated and some not. It seems that the plugin has
problems with several layers of parent POMs like we use it for the
different components.
I will open a new thread for this. This is really nagging me and I
would like to discuss how to start with a tooling that is helping us.
Best,
- Fabian
--
Fabian
http://twitter.com/fctwitt