The release is now complete. I was able to move the classes back into the old package
structure, and test the backwards compatibility of the runtime jar with tests weaved by
retro version 1.0.5, and everything seems to work fine.
The release notes can be found on the jira page:
http://jira.jboss.com/jira/secure/ReleaseNote.jspa?projectId=12310081&...
The groupId of jbossretro has changed from "jboss" to "org.jboss", so
the path is now a little different. If you want to use version 1.1.0 from an ant script,
you will have to put this into your build-thirdparty.xml
| <componentref name="org/jboss/jboss-retro"
version="1.1.0"/>
|
From a maven build, the dependency should look like this:
| <dependency>
| <groupId>org.jboss</groupId>
| <artifactId>jboss-retro</artifactId>
| <version>1.1.0</version>
| </dependency>
|
Or like this to include the runtime:
| <dependency>
| <groupId>org.jboss</groupId>
| <artifactId>jboss-retro</artifactId>
| <version>1.1.0</version>
| <classifier>rt</classifier>
| </dependency>
|
The jars are exactly the same whether you are using it from ant or maven, just a different
path to get there.
The maven-jboss-retro-plugin has also been released to verion 0.9-beta, and can be found
here:
http://repository.jboss.org/maven2/org/jboss/maven/plugins/maven-jboss-re...
The GA version 0.9 of the plugin will be coming soon, and will include some better
documentation about how to use the maven plugin to retro your code in a maven build.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4054491#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...