Re: How to build a release version of ApacheSling?

[th...@eknet.org]

Hi Robert and Bertrand,

thanks for your help. Now I finally managed to get it working. The 
reason why it failed was a typo in my Maven profile name (I do not want 
the apache-incubation project to be active by default) and a surefire 
plugin dependency from central seem to be used as the artifact 
org.apache.maven.plugins:maven-surefire-plugin:jar:9c6abc2 for the 
integration test project under 
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
get/test-classes/projects/normal/project/test-servlet-archetype-project. 
After I deleted the surefire plugin (under 
org/apache/maven/plugins/maven-surefire-plugin/9c6abc2 within my local 
repo) I could successfully build the project (after additionally passing 
the args -Dhttp.proxyHost as well as -Dhttp.proxyPort because at least 
one unit test tries to download artifacts from a springsource repository 
and i'm within a proxied environment).

So that means the process to create a new Sling release is to manually 
adjust the list.xml file, the version number of the launchpad project, 
triggering the maven-release-plugin and readjusting the version number 
to the next development version? Is the current released version 
Sling-6? And if so, is there a release plan for the next release 
Sling-7?

Thanks,
Stefan

Am 26.02.2014 13:40, schrieb Bertrand Delacretaz:
> Hi,
> 
> On Wed, Feb 26, 2014 at 11:54 AM, Robert Munteanu <ro...@lmn.ro> 
> wrote:
>> ...Presumably a released launchpad only references released artifacts, 
>> so
>> there should be no troubles with SNAPSHOTs....
> 
> FWIW that's not the case on trunk, there's lost of SNAPSHOTs in
> launchpad/builder/src/main/bundles/list.xml
> 
> -Bertrand

Re: How to build a release version of ApacheSling?

[Stefan Scheidewig <th...@eknet.org>]

... and I have to apologize for my last mail. My mail client seems to be 
broken :/

Greetings,
Stefan

Am 26.02.2014 14:00, schrieb thalis@eknet.org:
> Hi Robert and Bertrand,
> 
> thanks for your help. Now I finally managed to get it working. The
> reason why it failed was a typo in my Maven profile name (I do not
> want the apache-incubation project to be active by default) and a
> surefire plugin dependency from central seem to be used as the
> artifact org.apache.maven.plugins:maven-surefire-plugin:jar:9c6abc2
> for the integration test project under
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
> et/test-classes/projects/normal/project/test-servlet-archetype-project.
> 
> After I deleted the surefire plugin (under
> org/apache/maven/plugins/maven-surefire-plugin/9c6abc2 within my local
> repo) I could successfully build the project (after additionally
> passing the args -Dhttp.proxyHost as well as -Dhttp.proxyPort because
> at least one unit test tries to download artifacts from a springsource
> repository and i'm within a proxied environment).
> 
> So that means the process to create a new Sling release is to manually
> adjust the list.xml file, the version number of the launchpad project,
> triggering the maven-release-plugin and readjusting the version number
> to the next development version? Is the current released version
> Sling-6? And if so, is there a release plan for the next release
> Sling-7?
> 
> Thanks,
> Stefan
> 
> Am 26.02.2014 13:40, schrieb Bertrand Delacretaz:
>> Hi,
>> 
>> On Wed, Feb 26, 2014 at 11:54 AM, Robert Munteanu <ro...@lmn.ro> 
>> wrote:
>>> ...Presumably a released launchpad only references released 
>>> artifacts, so
>>> there should be no troubles with SNAPSHOTs....
>> 
>> FWIW that's not the case on trunk, there's lost of SNAPSHOTs in
>> launchpad/builder/src/main/bundles/list.xml
>> 
>> -Bertrand