<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Great, thanks for the update John. I'll try to organise the Seam
JCR release in the near future (tm).<br>
<br>
On 08/08/11 11:39, John D. Ament wrote:
<blockquote
cite="mid:CAOqetn8WperR=Smw65y2mohHCaxXs5=kXEGUoMhfZOMgUEjqwg@mail.gmail.com"
type="cite">Shane,<br>
<br>
Done on JMS for CR1 and is done on develop for JCR. Was trying to
ping you tonight, Seam JCR's ready for a Beta1 release, just in
time for 3.1 Beta1.<br>
<br>
John<br>
<br>
<div class="gmail_quote">On Sun, Aug 7, 2011 at 7:39 PM, Shane
Bryzak <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:sbryzak@redhat.com">sbryzak@redhat.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex;">Hi module
leads,<br>
<br>
In preparation for the 3.1.0.Beta1 release which we are
planning for<br>
this weekend, could you please take the following steps to
remove the<br>
combined jar from your module if you haven't already done so:<br>
<br>
1) Delete the "combined" directory from your module.<br>
<br>
2) Remove the combined module declaration from your module's
parent pom.xml<br>
<br>
3) Rename your module's implementation. If you have only one<br>
implementation then this should be simple - for example
seam-catch-impl<br>
will become just seam-catch. If you have more than one
implementation<br>
then name it likewise - e.g. seam-reports-jasper.<br>
<br>
4) Update the dependency management section of your parent
pom.xml - it<br>
will probably contain something like this:<br>
<br>
<dependency><br>
<groupId>org.jboss.seam.security</groupId><br>
<artifactId>seam-security-api</artifactId><br>
<version>${project.version}</version><br>
</dependency><br>
<br>
<dependency><br>
<groupId>org.jboss.seam.security</groupId><br>
<artifactId>seam-security-impl</artifactId><br>
<version>${project.version}</version><br>
</dependency><br>
<br>
<dependency><br>
<groupId>org.jboss.seam.security</groupId><br>
<artifactId>seam-security</artifactId><br>
<version>${project.version}</version><br>
</dependency><br>
<br>
<br>
In this example for Seam Security, the seam-security-impl
dependency<br>
should be removed (as the seam-security dependency will now
refer to the<br>
implementation).<br>
<br>
5) Update the dependencies for the distribution build. In
dist/pom.xml,<br>
you'll find dependencies for the api, impl and combined jar,
so like in<br>
step 4 you should be able to just delete the -impl dependency
to fix the<br>
dependency list.<br>
<br>
6) Update the assembly - edit
dist/src/main/assembly/assembly.xml, and<br>
update the dependencies, in particular the list of source
dependencies.<br>
<br>
7) Update your documentation - somewhere near the beginning of
most<br>
modules we list Maven dependencies, take a look at<br>
<a moz-do-not-send="true"
href="http://docs.jboss.org/seam/3/faces/latest/reference/en-US/html/faces.installation.html"
target="_blank">http://docs.jboss.org/seam/3/faces/latest/reference/en-US/html/faces.installation.html</a><br>
for an example. I'm open to suggestions for this however I
think the<br>
easiest thing we can instruct our users to do is simply add
the<br>
implementation dependency to their project, which will
automatically<br>
pull in the API.<br>
<br>
8) Build your module! Run mvn clean install -Drelease to
confirm that<br>
the distribution builds ok, and spend a few minutes checking
over the<br>
distribution archive to confirm that everything looks in
order.<br>
<br>
If you have any questions, please feel free to ask!<br>
<br>
Shane<br>
_______________________________________________<br>
seam-dev mailing list<br>
<a moz-do-not-send="true"
href="mailto:seam-dev@lists.jboss.org">seam-dev@lists.jboss.org</a><br>
<a moz-do-not-send="true"
href="https://lists.jboss.org/mailman/listinfo/seam-dev"
target="_blank">https://lists.jboss.org/mailman/listinfo/seam-dev</a><br>
</blockquote>
</div>
<br>
</blockquote>
<br>
</body>
</html>