Seam 3.0 roadmap
by Pete Muir
After last weeks IRC meeting, I now have a good understanding of where modules have got to.
http://seamframework.org/Seam3/Seam30Roadmap
Headlines:
* Aiming to get most modules to beta by end of Oct. A few (security, persistence, drools) likely still in alpha
* Beta of Seam 3 by 12th Nov in time for Devoxx
* Second beta in early December with all modules at beta
* First release candidate in early January
All module leads, please look at the roadmap and check that you can get your module to beta by then.
Ken, Shane, Jozef, still need to hear from you about when you can get International, Security and REST to beta -- please ping me.
Pete
12 years, 10 months
Seam RESTEasy renamed to Seam REST
by Pete Muir
Jozef has decided to target this module at the JAX-RS standard only, therefore the module name has changed slightly. We renamed the repo on github accordingly.
12 years, 11 months
Important: Module IMPL naming guidelines for upcoming Seam3 Beta release.
by Lincoln Baxter, III
According to the established ModuleAnatomy guidelines in the ModuleHandbook,
we should be using the following strategy for naming our artifacts:
http://seamframework.org/Seam3/ModuleAnatomy#H-Subprojects
*IMPL* (has compile dependency on API):
org.jboss.seam.*[module]*
*seam-[module]*
*API*:
org.jboss.seam.*[module]*
*seam-[module]-api*
But I see some modules that aren't following this. (Not going to call anyone
out.) I think it's a good idea that for the upcoming beta, we all try to
standardize our artifacts on this strategy to prevent confusion. I'd say the
folder structure can vary for now (should eventually be standardized if we
can manage it,) but the artifact IDs are very important to have together.
The key here is to make sure your impl is just the name of the seam-module.
That's what people will be consuming.
--
Lincoln Baxter, III
http://ocpsoft.com
http://scrumshark.com
"Keep it Simple"
12 years, 11 months
Permissions for pushing to github.com/seam repos
by Pete Muir
I have set up teams for each module, giving the lead permission to push to their repo (except in a couple of cases where I couldn't find the leads username, so if you can't push, then please tell me your username). You should now be able to handle pull request directly.
Let's see how this system works :-)
12 years, 11 months
sfwk.org and ir2 down
by Shane Bryzak
Both sites are down, and I can't SSH in either. Who do we need to
contact for support? I suspect they might have been down for some time
(last forums post was about 3 hours ago).
12 years, 11 months
Include the jboss repo in your root pom
by Pete Muir
Otherwise your builds fail. For example:
<profile>
<id>jboss-public-repository</id>
<!-- Repository is active unless explicitly disabled e.g. -P!jboss-public-repository -->
<activation>
<property>
<name>jboss-public-repository</name>
<value>!false</value>
</property>
</activation>
<repositories>
<repository>
<id>jboss-public-repository-group</id>
<name>JBoss Public Maven Repository Group</name>
<url>http://repository.jboss.org/nexus/content/groups/public</url>
<layout>default</layout>
<releases>
<enabled>true</enabled>
<updatePolicy>never</updatePolicy>
</releases>
<snapshots>
<enabled>false</enabled>
<updatePolicy>never</updatePolicy>
</snapshots>
</repository>
</repositories>
<pluginRepositories>
<pluginRepository>
<id>jboss-public-repository-group</id>
<name>JBoss Public Maven Repository Group</name>
<url>http://repository.jboss.org/nexus/content/groups/public</url>
<layout>default</layout>
<releases>
<enabled>true</enabled>
<updatePolicy>never</updatePolicy>
</releases>
<snapshots>
<enabled>true</enabled>
<updatePolicy>never</updatePolicy>
</snapshots>
</pluginRepository>
</pluginRepositories>
</profile>
12 years, 11 months
