7.1.3.Final of JBoss AS Archetypes released
by Rafael Benevides
Archetypes 7.1.3.Final was synched now with quickstarts (1.0.7.Final
BOMs) and just released.
--
Rafael Benevides | Senior Software Engineer
Red Hat Brazil
+55-61-9269-6576
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
10 years, 8 months
1.0.7.Final of JBoss BOMs released
by Rafael Benevides
As soon as it reaches Maven Central repo, I'll update Stacks.yaml and
all quickstarts to 1.0.7.Final
Thanks.
--
Rafael Benevides | Senior Software Engineer
Red Hat Brazil
+55-61-9269-6576
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
10 years, 8 months
Stacks 1.1 format proposal
by Rafael Benevides
Hi all,
As part of the "new organization" plan, it's a good time to update
stacks format since it will be hosted on the new github organization.
I've analyzed the changes need and attached a Stacks 1.1 proposal to see
if everyone agrees on that or if should we keep using 1.0 format
Changes from 1.0 to 1.1
- Rename Licenses to Metadata
Justification: I've been using Licenses today as an metadata
section to avoid repeating metadatas like version, repositories,
licenses, etc:
https://github.com/jboss-jdf/jdf-stack/blob/1.0.0.Final/stacks.yaml#L21-L34
Workaround: Leave it as it is
- add repositoryURL and extraRepositories to BomVersion.
Justification: I've been using labels to to tag what
repositories are Required:
https://github.com/jboss-jdf/jdf-stack/blob/1.0.0.Final/stacks.yaml#L441
- Some BOMs needs more than one repo as JPP ( JPP is built on
top of EAP 6.0.1, but it is using RichFaces from WFK 2.1.0 that
is built on top of EAP 6.0.0)
Workaround: Create an standard tag called *repositories* and add
every non maven central repository required.
So I'd like to here your thoughts about it and analyze possible impacts
on this format change.
OBS.: Remember that stacks 1.0 repo is planned to be moved to
jboss-developer github organization. So it's a good change to update it.
The 1.0 and 1.1 should coexist for a while and maybe stacks-client
should have a "migration" feature to permit a smooth transition.
Thank you
--
Rafael Benevides | Senior Software Engineer
Red Hat Brazil
+55-61-9269-6576
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
10 years, 8 months
QSTools 1.2.0.CR7 released
by Rafael Benevides
This new release includes 3 new checkers and 1 fix.
Bug fix:
- JDF-462 - Fix for Maven 3.1
New Checkers:
- JDF-470 - permit ignored properties on unusedpropertieschecker - This
will ignore alone declaration of ' maven.compiler.source+target'
- JDF-471 - Checks for invalid 'maven-compiler-plugin' declarations and
the presence of 'maven.compiler.source+target'
- Created RepositoryDeclarationChecker - Checks for invalid declaration
of repositories inside pom.xml
-
--
Rafael Benevides | Senior Software Engineer
Red Hat Brazil
+55-61-9269-6576
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
10 years, 8 months
QSTools 1.2.0.CR6 released
by Rafael Benevides
This release permits to exclude files only for specific Checkers.
For example, Petclinic is known as having original License Headers and
it shouldn't be changed. That caused many violations on QSTools but if
we add it to the general ignore list we loose TabSpaceChecker,
IndentationChecker, IllegalCharacterChecker, etc.
Now It's possible to ignore the files just for specific a Checker like
on
https://github.com/jboss-developer/maven-qstools-plugin/blob/e22ba29f0f75...
that excludes Petclinic only for FileHeaderChecker.
Enjoy!
--
Rafael Benevides | Senior Software Engineer
Red Hat Brazil
+55-61-9269-6576
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
10 years, 8 months
Quickstart Pull Status Report - 2013-08-22
by Sande Gilda
Due to the impending reorg, I am sending an updated report to let
everyone know the status of the outstanding pull requests. Note the
quickstarts with the orange background were closed and will be reopened
after the reorg is complete.
Please let me know if you have any questions or concerns.
Key:
Rows with green background need code review.
Rows with yellow background are waiting for the contributor.
Rows with white background need something out of our control, for
example, Maven or 3rd party updates.
Closed until after the reorg.
*Pull* *Quickstart Name* *Contributor* *Status* *Details*
317 <https://github.com/jboss-jdf/jboss-as-quickstart/pull/317>
ejb-timer Ondra Zizka Waiting for developer Ondra is trying to finish
this one up. It needs review when complete.
439 <https://github.com/jboss-jdf/jboss-as-quickstart/pull/439>
cdi-portable-extension-drools Marco Battaglia Waiting for developer
Code compiles, but tests fail. Postponed until after the reorg.
445 <https://github.com/jboss-jdf/jboss-as-quickstart/pull/445>
hornetq-clustering Jesse Sightler Waiting for developer Waiting for
Jesse to supply remove-*.cli scripts to clean up server changes done by
the install-*.cli scripts. Jess closed the pull.
463 <https://github.com/jboss-jdf/jboss-as-quickstart/pull/463>
servlet-security-genericheader-auth Jesse Sightler Waiting for
developer Waiting for Jesse to make the updates suggested by James
Perkins during the code review. Arquillian tests don't work. Jess closed
this pull.
478 <https://github.com/jboss-jdf/jboss-as-quickstart/pull/478>
kitchensink (functional tests) Stefan Miklosovic Waiting for
developer This one needs some modifications to work. Marek Schmidt
requested we close this for now. They will reopen it when it is ready.
485 <https://github.com/jboss-jdf/jboss-as-quickstart/pull/485>
booking-mvc-spring Tejas Mehta Waiting for developer This has been
rebased to the Spring source. Joshua reviewed this and found issues.
Tejas will not have time before the reorg. Closing for now.
560 <https://github.com/jboss-jdf/jboss-as-quickstart/pull/560>
kitchensink-grails Tejas Mehta Waiting for developer Joshu reviewed
this one and found POM file issues and missing validation for a missing
phone number. Tejas will not have time to modify before reorg. Closing
for now.
562 <https://github.com/jboss-jdf/jboss-as-quickstart/pull/562> Code
updates and changes to the instructions for the ejb-multi-server
Wolf-Dieter Fink Waiting for developer Tested and works fine. Has had
code review. Needs code formatting and license fixes reported by QS
Tools utility.
574 <https://github.com/jboss-jdf/jboss-as-quickstart/pull/574>
ejb-security-propagation Claudio Miranda Needs code review Sent
edited README file to Claudio. It works great. It still needs the README
update and fixes reported by QS tools, but is ready for code review.
584 <https://github.com/jboss-jdf/jboss-as-quickstart/pull/584>
picketlink quickstarts submodule Pedro Igor Needs code review Tested
and they all work fine. The 4 new quickstarts need code review:
picketlink-authentication-form,
picketlink-authentication-http-client-cert,
picketlink-authentication-recaptcha, and picketlink-authorization-idm-ldap
Like (0 <https://docspace.corp.redhat.com/docs/DOC-149498#>)
10 years, 8 months
WFK 2.1 BOMs on Stacks.yaml
by Rafael Benevides
Since I'm about to work on new organization and Stacks 1.1 format I'd
like to check with you guys about keeping the WFK 2.1 BOMs on stacks.yaml
WFK 2.1 BOMs uses a different groupdId (com.redhat.jboss.wfk.boms) which
seems that was used only on WFK 2.1
Now that we're moving to org.jboss.bom(eap|wfk|etc) I'd like to cleanup
those WFK 2.1 BOMs and just keep WFK 2.2 and WFK 2.3 BOMs. Is that
something that I could do without causing any impacts ?
Thanks
--
Rafael Benevides | Senior Software Engineer
Red Hat Brazil
+55-61-9269-6576
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
10 years, 8 months
