clerezza-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Reto Bachmann-Gmür <r...@apache.org>
Subject Re: [jira] [Resolved] (CLEREZZA-771) Release jaxrs.utils 0.7
Date Thu, 18 Apr 2013 03:45:52 GMT
Hi Giuseppe

Thanks for pointing to this. We removed internal dependencies from the
parent's dependency management as to make releasing individual modules
easier.

The idea is that whenever a dependency is released all the other modules
are updated to depend on the new version. This shouldn't be a lot of work
but just running

 mvn org.codehaus.mojo:versions-maven-plugin:2.0:use-latest-versions
"-Dincludes=org.apache.clerezza:jaxrs.utils:*:*" -DexcludeReactor=false
-DgenerateBackupPoms=false  -DallowSnapshots=true

not sure what I did the first time. Updating dependencies it shouldn't have
updates and - as you noticed - omitting many it should have.

Note that  the the artifact name in "includes" needs currently to be
specifies as the incubating version number is considered to be higher.

Cheers,
reto


On Wed, Apr 17, 2013 at 6:01 PM, Giuseppe Miscione <
g.miscione@innovationengineering.eu> wrote:

> Also platform.content, platform.accountcontrolpanel.**core,
> platform.concepts.core, platform.content.**representations.core,
> platform.curieprefixmanager.**core, platform.dashboard.**webinterface,
> platform.documentation.viewer, platform.logging.core, platform.usermanager.
> **webinterface, rdf.web.core, platform.launcher.storageless.**parent,
> tools.offline, uima.samples are still depending on 0.7-SNAPSHOT.
>
> Shouldn't be easier to use maven dependency management in parent pom to
> track these version dependencies instead of repeating the setting in all
> requiring modules?
>
> Il 17/04/2013 17:29, Giuseppe Miscione ha scritto:
>
>  Hi Reto,
>> I noticed that the trunk version of platform.dashboard.core still depends
>> on jaxrs.utils version 0.7-SNAPSHOT.
>>
>> Regards,
>> Giuseppe
>>
>> Il 17/04/2013 10:01, Reto Bachmann-Gmür (JIRA) ha scritto:
>>
>>>       [ https://issues.apache.org/**jira/browse/CLEREZZA-771?page=**
>>> com.atlassian.jira.plugin.**system.issuetabpanels:all-**tabpanel<https://issues.apache.org/jira/browse/CLEREZZA-771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel>]
>>>
>>> Reto Bachmann-Gmür resolved CLEREZZA-771.
>>> ------------------------------**-----------
>>>
>>>      Resolution: Fixed
>>>
>>> 0.7 released and all trunk versions are now using 0.8-SNAPSHOT
>>>
>>>> Release jaxrs.utils 0.7
>>>> -----------------------
>>>>
>>>>                  Key: CLEREZZA-771
>>>>                  URL: https://issues.apache.org/**
>>>> jira/browse/CLEREZZA-771<https://issues.apache.org/jira/browse/CLEREZZA-771>
>>>>              Project: Clerezza
>>>>           Issue Type: Task
>>>>             Reporter: Reto Bachmann-Gmür
>>>>             Assignee: Reto Bachmann-Gmür
>>>>
>>>> The old version of the Multipart Form doesn't work when another
>>>> MesssageBodyReader for the same MediaType is in place. This has been an
>>>> issue for using the bundle in Stanbol and has been fixed with CLEREZZA-738.
>>>>
>>> --
>>> This message is automatically generated by JIRA.
>>> If you think it was sent incorrectly, please contact your JIRA
>>> administrators
>>> For more information on JIRA, see: http://www.atlassian.com/**
>>> software/jira <http://www.atlassian.com/software/jira>
>>>
>>>
>>
>>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message