Warnings when compiling WildFly
by Juergen Zimmermann
I just downloaded the sources of WildFly Core and WildFly. The compilations
are working fine. However, for WildFly I'm getting these warnings right at
the beginning:
[WARNING] Some problems were encountered while building the effective model
for org.wildfly:wildfly-ts-integ-smoke:jar:9.0.0.Alpha1-SNAPSHOT
[WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)'
must be unique: org.jboss.arquillian.junit:arquillian-junit-container:jar ->
duplicate declaration of version (?) @
org.wildfly:wildfly-testsuite:9.0.0.Alpha1-SNAPSHOT,
C:\temp\wildfly-master-20140703\testsuite\pom.xml, line 215, column 21
[WARNING]
[WARNING] Some problems were encountered while building the effective model
for org.wildfly:wildfly-ts-integ:pom:9.0.0.Alpha1-SNAPSHOT
[WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)'
must be unique: org.jboss.arquillian.junit:arquillian-junit-container:jar ->
duplicate declaration of version (?) @
org.wildfly:wildfly-testsuite:9.0.0.Alpha1-SNAPSHOT,
C:\temp\wildfly-master-20140703\testsuite\pom.xml, line 215, column 21
[WARNING]
[WARNING] Some problems were encountered while building the effective model
for org.wildfly:wildfly-testsuite:pom:9.0.0.Alpha1-SNAPSHOT
[WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)'
must be unique: org.jboss.arquillian.junit:arquillian-junit-container:jar ->
duplicate declaration of version (?) @ line 215, column 21
[WARNING]
[WARNING] It is highly recommended to fix these problems because they
threaten the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support
building such malformed projects.
11 years, 10 months
Pending core split
by Stuart Douglas
Hi all,
So I am moderately confident that we will be ready to split out Wildfly
core into a separate repository early next week (I'm not saying that it
will definitely happen in this time frame, just that it should be possible).
Once this is ready to go I think the basic process will be:
- Code freeze on Master
- Create the core repo, push new rewritten core history
- Release core 1.0.0.Beta1
- Create PR against core WF repo that deletes everything in core, and
uses the core 1.0.0.Beta1 release
- End of code freeze
Stuart
11 years, 10 months
Build split stage one is complete
by Stuart Douglas
Hi all,
The first stage of the build split has been commited. We now have a
wildfly-core repository at https://github.com/wildfly/wildfly-core, and
the main Wildfly build now builds using artifacts produced from this.
There is still a *lot* of work to do:
- Remove Arquillian (there should be nothing stopping this now)
- Split up the current build tool into build/provisioning tools,
including creating a WF feature pack format
- Further split up, the first of which will be a feature pack that
corresponds to the current web-build module (although IMHO we should
wait a little bit to see if there are any issues with the current split
before pressing ahead with this)
- General cleanup of dependencies that are no longer needed
Stuart
11 years, 10 months
Documentation to get started?
by Chris Kujawa
Hello.
My name is Chris. I'm a Java developer with over 10 years of commercial
experience (and more as a hobbyist) and I was recently looking for an
open-source project to contribute to so I can give something back to the
community--and since I frequently use jBoss I thought Wildfly just might be
the thing. I've worked my way through the "Hacking on Wildfly" page and
thought that WFLY-717
<https://issues.jboss.org/browse/WFLY-717?jql=project%20%3D%20WFLY%20AND%2...>
(Add
ability to launch H2 console...) might be a good place to start. So I
started poking around looking for where I might add such a link and can't
seem to work out how the "App.html" page is built in the admin console. Is
there documentation that I've missed that would walk me through this
process?
Additionally, I thought that the "home" section might be a good place to
add such a link, since the other panels all seem to contain Wildfly
specific functionality. Or...perhaps I could add a new panel (H2 or even
Utilities) and add the link there...thoughts?
Thank you in advance...and I'm looking forward to giving back to this great
tool that I've used many times in the past!
-Chris
11 years, 10 months
