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/01/30 11:56:21 UTC
STANBOL-888 and bundle-lists
Hello
I've jus run into problems because of trunk bundle-lists pointing to
snapshot versions no longer in trunk. With the moving of the bundle-lists
done in STANBOL-806 it is no longer clear when the bundle-list should be
updated. I think it would be handy for integrators that when the commons
bundles are released that the bundle-list ist relased as well so that it
becomes easy to use all the released bundles in an integrating launcher
(even if stanbol itself does not release such a lanucher). If no such
bundllelist is released (which makes the release of the bundles of less
value) the trunk version should at least be updated to use the new snapshot
version. I'll open an issue to change the versions changed within
STANBOL-888 in the bundlelists.
Cheers,
Reto
Re: STANBOL-888 and bundle-lists
Posted by Fabian Christ <ch...@googlemail.com>.
2013/1/30 Reto Bachmann-Gmür <re...@apache.org>:
> Ideally of course this would be handled by the release plugin or the
> launchpab plugin wouldhave the versions specified in the pom rather than in
> the separate xml.
If you know of any tool support for this, let me know.
The release plugin is not aware of the existence of the list.xml
files. We are missing something like OSGi release support with Maven.
--
Fabian
http://twitter.com/fctwitt
Re: STANBOL-888 and bundle-lists
Posted by Rupert Westenthaler <ru...@gmail.com>.
Hi
With revision 1441720 [1] I committed the upgrade to the
maven-launchpad-plugin 2.2.0. Also upgraded some additional
dependencies. Build on my machine was fine. Lets see if Jenkins is
also happy.
I have already started with a complete reorganization of the bundle
lists that should it make much easier to create customized Stanbol
Launchers. This new model uses maven dependencies between bundle lists
to ensure that each bundle list is self consistent.
The final goal is to provide users the possibility to build launchers
based on desired features e.g.
* "Core Stanbol Runtime" with the
* "OpenNLP NLP processing engines" the
* "Entityhub based EntityLinking Engine" and the
* "Enthityhub Solr based Storage" to store his Vocabularies using the SolrYard
and he will get an Stanbol Launcher that includes all modules required
to have exactly those features.
The current Stanbol Component based Launcher configurations will still
be supported by the definition of default bundlelists for components.
By using those lists user will still be able to create a launcher like
* "Core Stanbol Runtime"
* "Stanbol Enhancer"
* "Stanbol Entityhub"
* "Stanbol Contenthub"
and possibly adding cross cutting features such as
* "Security" and
* "zzShell"
As this new model requires the Apache Sling maven-launchpad-plugin to
support transitive dependencies defined between partialbundlelists I
created SLING-2722 [2] and provided a patch.
best
Rupert
[1] http://svn.apache.org/viewvc?rev=1441720&view=rev
[2] https://issues.apache.org/jira/browse/SLING-2722
On Fri, Feb 1, 2013 at 8:52 AM, Fabian Christ
<ch...@googlemail.com> wrote:
> 2013/1/31 Reto Bachmann-Gmür <re...@apache.org>:
>> Ok the parent seems to be updated with the following:
>>
>> mvn versions:update-parent -DallowSnapshots=true
>>
>> To me it seems this should be done when the parent changes version to make
>> sure that relative-path and version remain consistent. WDYT?
>
> +1
>
>
> --
> Fabian
> http://twitter.com/fctwitt
--
| 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/1/31 Reto Bachmann-Gmür <re...@apache.org>:
> Ok the parent seems to be updated with the following:
>
> mvn versions:update-parent -DallowSnapshots=true
>
> To me it seems this should be done when the parent changes version to make
> sure that relative-path and version remain consistent. WDYT?
+1
--
Fabian
http://twitter.com/fctwitt
Re: STANBOL-888 and bundle-lists
Posted by Reto Bachmann-Gmür <re...@apache.org>.
On Thu, Jan 31, 2013 at 2:22 PM, Reto Bachmann-Gmür <re...@apache.org> wrote:
> I'm having quite weird problem when integrating stanbol in a reactor
> containing othe partialbundlelists. 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?
>
> And a related question: id I update the version in the parent how do I
> make sure the projects are actually using it? Right now we have modules
> uing older version even though they have a relativePath pointing to the
> newest version.
>
Ok the parent seems to be updated with the following:
mvn versions:update-parent -DallowSnapshots=true
To me it seems this should be done when the parent changes version to make
sure that relative-path and version remain consistent. WDYT?
Reto
>
> Cheers,
> Reto
>
>
>
> On Jan 31, 2013 10:57 AM, "Rupert Westenthaler" <
> rupert.westenthaler@gmail.com> wrote:
>
>> FYI: I have started to work on the bundle lists. In a first iteration
>> I will update dependencies to the newest versions. Structural changes
>> will come earliest in an 2nd iteration.
>>
>> best
>> Rupert
>>
>> On Wed, Jan 30, 2013 at 3:40 PM, Rupert Westenthaler
>> <ru...@gmail.com> wrote:
>> > Hi
>> >
>> > I think a branch for bundlelists is actually a good idea. Because we
>> > might want to release updated bundle lists in case of maintenance
>> > release ( =.=.+ ) of modules. If we do not create a branch it would be
>> > very hard to release upgraded bundle lists and launchers that include
>> > those modules.
>> >
>> > If you like I can have a look at the bundle lists. I plan to make some
>> > improvements/changes to them anyway (e.g. ripping of the
>> > enhancement-engines from the enhancer bundle list in favor of an own
>> > bundle list(s) for enhancement engines.
>> >
>> > best
>> > Rupert
>> >
>> >
>> > On Wed, Jan 30, 2013 at 3:16 PM, Reto Bachmann-Gmür <re...@apache.org>
>> wrote:
>> >> On Wed, Jan 30, 2013 at 3:08 PM, Fabian Christ <
>> christ.fabian@googlemail.com
>> >>> wrote:
>> >>
>> >>> 2013/1/30 Fabian Christ <ch...@googlemail.com>:
>> >>> > Release of stable launcher configurations and bundle lists comes
>> next.
>> >>>
>> >>> BTW, if there is someone who wants to work on this, help is very
>> welcome.
>> >>>
>> >>> Since the bundle lists in the trunk are all pointing to SNAPSHOT
>> >>> versions, the work on bundlelists with fixed bundle versions should be
>> >>> done in a branch. Or how do you think should we proceed with the
>> >>> bundle lists?
>> >>>
>> >> I don't see a big problem if the bunlelists in trunk temporarily point
>> to
>> >> the released version. Much better than pointing to the previous
>> snapshot.
>> >> Ideally of course this would be handled by the release plugin or the
>> >> launchpab plugin wouldhave the versions specified in the pom rather
>> than in
>> >> the separate xml.
>> >>
>> >> Cheers,
>> >> Reto
>> >>
>> >>
>> >>>
>> >>> Best,
>> >>> - Fabian
>> >>> --
>> >>> Fabian
>> >>> http://twitter.com/fctwitt
>> >>>
>> >
>> >
>> >
>> > --
>> > | 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 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
Re: STANBOL-888 and bundle-lists
Posted by Reto Bachmann-Gmür <re...@apache.org>.
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 Reto Bachmann-Gmür <re...@apache.org>.
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 Reto Bachmann-Gmür <re...@wymiwyg.com>.
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
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 Reto Bachmann-Gmür <re...@apache.org>.
I'm having quite weird problem when integrating stanbol in a reactor
containing othe partialbundlelists. 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?
And a related question: id I update the version in the parent how do I make
sure the projects are actually using it? Right now we have modules uing
older version even though they have a relativePath pointing to the newest
version.
Cheers,
Reto
On Jan 31, 2013 10:57 AM, "Rupert Westenthaler" <
rupert.westenthaler@gmail.com> wrote:
> FYI: I have started to work on the bundle lists. In a first iteration
> I will update dependencies to the newest versions. Structural changes
> will come earliest in an 2nd iteration.
>
> best
> Rupert
>
> On Wed, Jan 30, 2013 at 3:40 PM, Rupert Westenthaler
> <ru...@gmail.com> wrote:
> > Hi
> >
> > I think a branch for bundlelists is actually a good idea. Because we
> > might want to release updated bundle lists in case of maintenance
> > release ( =.=.+ ) of modules. If we do not create a branch it would be
> > very hard to release upgraded bundle lists and launchers that include
> > those modules.
> >
> > If you like I can have a look at the bundle lists. I plan to make some
> > improvements/changes to them anyway (e.g. ripping of the
> > enhancement-engines from the enhancer bundle list in favor of an own
> > bundle list(s) for enhancement engines.
> >
> > best
> > Rupert
> >
> >
> > On Wed, Jan 30, 2013 at 3:16 PM, Reto Bachmann-Gmür <re...@apache.org>
> wrote:
> >> On Wed, Jan 30, 2013 at 3:08 PM, Fabian Christ <
> christ.fabian@googlemail.com
> >>> wrote:
> >>
> >>> 2013/1/30 Fabian Christ <ch...@googlemail.com>:
> >>> > Release of stable launcher configurations and bundle lists comes
> next.
> >>>
> >>> BTW, if there is someone who wants to work on this, help is very
> welcome.
> >>>
> >>> Since the bundle lists in the trunk are all pointing to SNAPSHOT
> >>> versions, the work on bundlelists with fixed bundle versions should be
> >>> done in a branch. Or how do you think should we proceed with the
> >>> bundle lists?
> >>>
> >> I don't see a big problem if the bunlelists in trunk temporarily point
> to
> >> the released version. Much better than pointing to the previous
> snapshot.
> >> Ideally of course this would be handled by the release plugin or the
> >> launchpab plugin wouldhave the versions specified in the pom rather
> than in
> >> the separate xml.
> >>
> >> Cheers,
> >> Reto
> >>
> >>
> >>>
> >>> Best,
> >>> - Fabian
> >>> --
> >>> Fabian
> >>> http://twitter.com/fctwitt
> >>>
> >
> >
> >
> > --
> > | 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 Rupert Westenthaler <ru...@gmail.com>.
FYI: I have started to work on the bundle lists. In a first iteration
I will update dependencies to the newest versions. Structural changes
will come earliest in an 2nd iteration.
best
Rupert
On Wed, Jan 30, 2013 at 3:40 PM, Rupert Westenthaler
<ru...@gmail.com> wrote:
> Hi
>
> I think a branch for bundlelists is actually a good idea. Because we
> might want to release updated bundle lists in case of maintenance
> release ( =.=.+ ) of modules. If we do not create a branch it would be
> very hard to release upgraded bundle lists and launchers that include
> those modules.
>
> If you like I can have a look at the bundle lists. I plan to make some
> improvements/changes to them anyway (e.g. ripping of the
> enhancement-engines from the enhancer bundle list in favor of an own
> bundle list(s) for enhancement engines.
>
> best
> Rupert
>
>
> On Wed, Jan 30, 2013 at 3:16 PM, Reto Bachmann-Gmür <re...@apache.org> wrote:
>> On Wed, Jan 30, 2013 at 3:08 PM, Fabian Christ <christ.fabian@googlemail.com
>>> wrote:
>>
>>> 2013/1/30 Fabian Christ <ch...@googlemail.com>:
>>> > Release of stable launcher configurations and bundle lists comes next.
>>>
>>> BTW, if there is someone who wants to work on this, help is very welcome.
>>>
>>> Since the bundle lists in the trunk are all pointing to SNAPSHOT
>>> versions, the work on bundlelists with fixed bundle versions should be
>>> done in a branch. Or how do you think should we proceed with the
>>> bundle lists?
>>>
>> I don't see a big problem if the bunlelists in trunk temporarily point to
>> the released version. Much better than pointing to the previous snapshot.
>> Ideally of course this would be handled by the release plugin or the
>> launchpab plugin wouldhave the versions specified in the pom rather than in
>> the separate xml.
>>
>> Cheers,
>> Reto
>>
>>
>>>
>>> Best,
>>> - Fabian
>>> --
>>> Fabian
>>> http://twitter.com/fctwitt
>>>
>
>
>
> --
> | 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 Rupert Westenthaler <ru...@gmail.com>.
Hi
I think a branch for bundlelists is actually a good idea. Because we
might want to release updated bundle lists in case of maintenance
release ( =.=.+ ) of modules. If we do not create a branch it would be
very hard to release upgraded bundle lists and launchers that include
those modules.
If you like I can have a look at the bundle lists. I plan to make some
improvements/changes to them anyway (e.g. ripping of the
enhancement-engines from the enhancer bundle list in favor of an own
bundle list(s) for enhancement engines.
best
Rupert
On Wed, Jan 30, 2013 at 3:16 PM, Reto Bachmann-Gmür <re...@apache.org> wrote:
> On Wed, Jan 30, 2013 at 3:08 PM, Fabian Christ <christ.fabian@googlemail.com
>> wrote:
>
>> 2013/1/30 Fabian Christ <ch...@googlemail.com>:
>> > Release of stable launcher configurations and bundle lists comes next.
>>
>> BTW, if there is someone who wants to work on this, help is very welcome.
>>
>> Since the bundle lists in the trunk are all pointing to SNAPSHOT
>> versions, the work on bundlelists with fixed bundle versions should be
>> done in a branch. Or how do you think should we proceed with the
>> bundle lists?
>>
> I don't see a big problem if the bunlelists in trunk temporarily point to
> the released version. Much better than pointing to the previous snapshot.
> Ideally of course this would be handled by the release plugin or the
> launchpab plugin wouldhave the versions specified in the pom rather than in
> the separate xml.
>
> Cheers,
> Reto
>
>
>>
>> Best,
>> - Fabian
>> --
>> Fabian
>> http://twitter.com/fctwitt
>>
--
| Rupert Westenthaler rupert.westenthaler@gmail.com
| Bodenlehenstraße 11 ++43-699-11108907
| A-5500 Bischofshofen
Re: STANBOL-888 and bundle-lists
Posted by Reto Bachmann-Gmür <re...@apache.org>.
On Wed, Jan 30, 2013 at 3:08 PM, Fabian Christ <christ.fabian@googlemail.com
> wrote:
> 2013/1/30 Fabian Christ <ch...@googlemail.com>:
> > Release of stable launcher configurations and bundle lists comes next.
>
> BTW, if there is someone who wants to work on this, help is very welcome.
>
> Since the bundle lists in the trunk are all pointing to SNAPSHOT
> versions, the work on bundlelists with fixed bundle versions should be
> done in a branch. Or how do you think should we proceed with the
> bundle lists?
>
I don't see a big problem if the bunlelists in trunk temporarily point to
the released version. Much better than pointing to the previous snapshot.
Ideally of course this would be handled by the release plugin or the
launchpab plugin wouldhave the versions specified in the pom rather than in
the separate xml.
Cheers,
Reto
>
> Best,
> - Fabian
> --
> Fabian
> http://twitter.com/fctwitt
>
Re: STANBOL-888 and bundle-lists
Posted by Fabian Christ <ch...@googlemail.com>.
2013/1/30 Fabian Christ <ch...@googlemail.com>:
> Release of stable launcher configurations and bundle lists comes next.
BTW, if there is someone who wants to work on this, help is very welcome.
Since the bundle lists in the trunk are all pointing to SNAPSHOT
versions, the work on bundlelists with fixed bundle versions should be
done in a branch. Or how do you think should we proceed with the
bundle lists?
Best,
- Fabian
--
Fabian
http://twitter.com/fctwitt
Re: STANBOL-888 and bundle-lists
Posted by Fabian Christ <ch...@googlemail.com>.
Hi,
meanwhile with STANBOL-900-903 even more bundles got released and the
versions need to be updated.
I am currently working on this.
Release of stable launcher configurations and bundle lists comes next.
- Fabian
2013/1/30 Reto Bachmann-Gmür <re...@apache.org>:
> Hello
>
> I've jus run into problems because of trunk bundle-lists pointing to
> snapshot versions no longer in trunk. With the moving of the bundle-lists
> done in STANBOL-806 it is no longer clear when the bundle-list should be
> updated. I think it would be handy for integrators that when the commons
> bundles are released that the bundle-list ist relased as well so that it
> becomes easy to use all the released bundles in an integrating launcher
> (even if stanbol itself does not release such a lanucher). If no such
> bundllelist is released (which makes the release of the bundles of less
> value) the trunk version should at least be updated to use the new snapshot
> version. I'll open an issue to change the versions changed within
> STANBOL-888 in the bundlelists.
>
> Cheers,
> Reto
--
Fabian
http://twitter.com/fctwitt