You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wicket.apache.org by Michael O'Cleirigh <mi...@rivulet.ca> on 2010/05/23 05:50:35 UTC

I am in the process of staging wicketstuff-core 1.4.7 release which has broken team city builds for 1.4.8-SNAPSHOT

Hello,

I've been working through the process to stage a release for 
wicketstuff-core 1.4.7.  I ran the maven release plugin and have tagged 
a 1.4.7 release and changed trunk to 1.4.8-SNAPSHOT version.

According to the team city emails I've been receiving there are projects 
that depend on wicketstuff-core that can still be built and these are 
breaking because 1.4.8-SNAPSHOT is not available.

I've just done a snapshot build into the oss.sonatype.org repository 
that I thought would fix the problem but it hasn't.  It looks like 
because I've added a profile into the parent wicketstuff-core pom to 
lookup snapshots from oss.sonatype.org it is not working when the 
project is compiled separately (like how teamcity is seems to be 
working).  (wicketstuff core is still broken on teamcity)

I'm not sure if these errors can be fixed within teamcity but I wanted 
to let everyone else know about why it is broken now.

However my Hudson server is now building every 15 minutes and the 
1.4.8-SNAPSHOT's are available through the oss.sonatype.org infrastructure.

The 1.4.8-SNAPSHOTS can be used if a <repository> entry is added like this:

<repositories>
  <repository>
      <id>nexus-snapshots</id>
       <name>Sonatype Nexus Snapshots</name>
        <url>http://oss.sonatype.org/content/repositories/snapshots</url>
        <snapshots><enabled>true</enabled></snapshots>
  </repository>
 </repositories>

There are other url's you can try aswell:
Download snapshot and release artifacts from group 
http://oss.sonatype.org/content/groups/public
Download snapshot, release and staged artifacts from staging group 
http://oss.sonatype.org/content/groups/staging

Once I have 1.4.7 staged I will post another mail for a release vote.  
Once 1.4.7 is promoted it will be available from the central maven 
repository.  Part of the delay right now is fixing the pom's to fit the 
central sync up requirements.

Regards,

Mike