[
https://issues.apache.org/jira/browse/QPID-5048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13914583#comment-13914583
]
Justin Ross commented on QPID-5048:
-----------------------------------
I like qpid-parent-pom a lot better. I feel like I know what it is when I scan
the stuff under asf/qpid/.
To explain, my concern comes from the position of someone looking at the
following output and trying to figure out what each thing is.
{noformat}
[jross@localhost ~]$ svn ls http://svn.apache.org/repos/asf/qpid/
branches/
dispatch/
doap_qpid.rdf
jms/
proton/
qpid-parent/
site/
tags/
trunk/
{noformat}
Everything there is fairly well distinguished except for qpid-parent.
(Branches, tags, and trunk mixed in is somewhat confusing, but we know why that
is.) Not a big deal. I'm just interested in talking about these decsisions so
we avoid some confusion. qpid-parent-pom solves it for me.
> [Java] Implement a Maven 3 build system
> ----------------------------------------
>
> Key: QPID-5048
> URL: https://issues.apache.org/jira/browse/QPID-5048
> Project: Qpid
> Issue Type: Task
> Components: Build Tools
> Reporter: Rob Godfrey
> Assignee: Robbie Gemmell
> Attachments:
> 0001-QPID-5048-Maven-POM-refactoring-names-descriptions-d.patch,
> 0001-QPID-5048-Maven-enahancements-to-restructure-POM-hie.patch,
> 0001-QPID-5048-Moved-slf4j-deps-to-test-utils-to-workarou.patch,
> 0002-QPID-5048-Logging-dependency-and-configuration-tidy-.patch,
> 0003-QPID-5048-logging-and-build-output-cleanup.patch
>
>
> Implement a Maven build system which generates the same artefacts as the
> current ant based build.
> See: https://cwiki.apache.org/confluence/display/qpid/Java+Build+System
> TO DO
> - Add the Excludes files, log4j config, etc test resources to a module
> (qpid-test-utils?) which can be
> used (extracted?) by the others to prevent them having to reference outside
> their directly for the files.
> - Fix what the systests/perftests do to copy the test-profiles dir to the
> necessary location.
> - Test deploying the modules to a local Nexus instance (by overriding the
> repo properties locally).
> - Ensure we dont deploy modules we aren't already doing so, it will make
> changing them later less of a pain for everyone.
> - Add the other test profiles, e.g. derby and other protocols.
> - Generate HTML reports of the test results
> - Decide on how to handle the surefire report target re-running the tests
> (there is a report-only task that doesnt, provided as a workaround)
> - Add LICENCE, NOTICE, README files to the binary assemblies.
> - Align the XML in the pom files consistently, fix whitepsace errors.
> === Once the Ant build is removed ===
> - Move all the resources to be in the /src/foo/resources folders.
> - Make qpidversion.properties in common be a filtered resource instead of
> generated.
> - Get rid of the antrun-plugin execution in common, directly invoke the
> required java elements.
> - Do the above in the generate-sources-common profile instead of current
> default config.
> - Get rid of the antrun-plugin execution in broker-core, directly invoke the
> required java elements.
> - Fix the tests not to be dependant on the working dir being the java dir.
> - Fix the tests not to be dependant on the test config/output dirs being
> children of qpid.home.
> - Remove the QBTC output file mechanics, rely on Surefire to do it?
> - JUnit test profiles instead of Exludes files?
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
